Builds terminating without (known) cause |
|
Issue descriptionSeveral builds have terminated with terminated without a known cause, for example: https://ci.chromium.org/p/chromeos/builders/luci.chromeos.general/PreCQ/b8931139331183287696 Need to root cause why these were canceled, if possible. Might be a dup of crbug.com/898996 Note that I will only be online intermittently for the rest of the week.
,
Nov 1
The task reports as "KILLED", but I don't see where/why, and I thought that was recorded on the task. https://chrome-swarming.appspot.com/task?id=40e3818fee0f8310&refresh=10&show_raw=1&wide_logs=true Looking up the build in buildbucket I see "CANCELLED EXPLICITLY", but I don't see what did it, and was expecting some reason to be recorded. https://apis-explorer.appspot.com/apis-explorer/?base=https://cr-buildbucket.appspot.com/_ah/api#p/buildbucket/v1/buildbucket.get?id=8931139331183287696&_h=1& https://chrome-swarming.appspot.com/bot?id=swarm-cros-78&sort_stats=total%3Adesc
,
Nov 1
Chromite's buildbucket cancel code doesn't support passing a reason: https://chromium.git.corp.google.com/chromiumos/chromite/+/c281275a4ce0cc08909d42958cc4fb9aef107fa8/lib/buildbucket_lib.py#298 The v2 API has an explicit reason field. I imagine the equivalent would be to pass something for "result_details_json" in the v1 cancel request. |
|
►
Sign in to add a comment |
|
Comment 1 by athilenius@chromium.org
, Nov 1