Milo should expose that swarming hardfailed task |
|||||
Issue descriptionConsider https://luci-milo.appspot.com/p/boringssl/builders/luci.boringssl.try/win64_vs2017_compile/b8943797411569763952 It says "Failed" but all steps are green. No step log says anything. That's because kitchen finished just fine. Swarming, however, failed the build anyway because of unfinished process preventing removal of some files [1]. This must be made clear. Maybe, adding fake step at the end "post-task cleanup failure on swarming" and linking to swarming task? [1] https://chromium-swarm.appspot.com/task?id=3e13fa414db3a810&refresh=10&show_raw=1&wide_logs=true
,
Jun 14 2018
M-A, kitchen exited with 0 (I believe), but the exit code is set to 1 because kitchen is wrapped. Is this inconsistency intentional? We seem to conflate exit code of a user-defined program (kitchen) and swarming internals. Can the exit code be left 0, but failure=true? With an explanation of why failure is true, e.g. "exit code is not zero" or "some children processes were left running unattended". Although GUI of the task does display that human-consumable reasoning why task failed, I don't see similar info in TaskResult in API: https://apis-explorer.appspot.com/apis-explorer/?base=https://chromium-swarm.appspot.com/_ah/api#p/swarming/v1/swarming.task.result?task_id=3e13fa414db3a810&_h=1&
,
Jun 22 2018
,
Jun 22 2018
,
Oct 12
bump, this has puzzled yet another user (efoo@ , while helping NaCL to migrate to LUCI)
,
Oct 12
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by hinoka@chromium.org
, Jun 14 2018