milo build https://luci-milo-dev.appspot.com/swarming/task/34ca0e65b247d610?server=chromium-swarm-dev.appspot.com says that "compile (with patch)" step is purple.
However, the task log [1] says that it succeeded:

substep: <
  step: <
    name: "compile (with patch)"
    status: SUCCESS
    stdout_stream: <
      name: "steps/compile__with_patch_/0/stdout"
    >
    started: <
      seconds: 1489032721
      nanos: 430000128
    >
    ended: <
      seconds: 1489036094
      nanos: 190000128
    >
  >
>

and then there are other steps with substeps in the task log:

substep: <
  step: <
    name: "compile (with patch) confirm no-op"
    status: SUCCESS
    stdout_stream: <
      name: "steps/compile__with_patch__confirm_no-op/0/stdout"
    >
    started: <
      seconds: 1489036094
      nanos: 190000128
    >
    ended: <
      seconds: 1489036114
      nanos: 680000000
    >
  >
>
substep: <
  step: <
    name: "postprocess_for_goma"
    status: SUCCESS
    substep: <
      step: <
        name: "postprocess_for_goma.goma_jsonstatus"
        status: SUCCESS
        stdout_stream: <
          name: "steps/postprocess_for_goma/0/steps/goma_jsonstatus/0/stdout"
        >
        started: <
          seconds: 1489036114
          nanos: 680000000
        >
        ended: <
          seconds: 1489036115
          nanos: 410000128
        >
        other_links: <
          label: "json.output (invalid)"
          logdog_stream: <
            name: "steps/postprocess_for_goma/0/steps/goma_jsonstatus/0/logs/json.output__invalid_/0"
          >
        >
      >
    >
    substep: <
      step: <
        name: "postprocess_for_goma.write_jsonstatus"
        status: SUCCESS
        stdout_stream: <
          name: "steps/postprocess_for_goma/0/steps/write_jsonstatus/0/stdout"
        >
        started: <
          seconds: 1489036115
          nanos: 410000128
        >
        ended: <
          seconds: 1489036115
          nanos: 450000128
        >
      >
    >
   .......................



these are two problem, but possibly because of the same bug