LUCI buildbucket is confused after the swarming task was killed |
||||
Issue descriptionJob: https://luci-scheduler.appspot.com/jobs/v8/V8%20Linux64%20-%20builder Build: https://ci.chromium.org/p/v8/builders/luci.v8.ci/V8%20Linux64%20-%20builder/448 Task: https://chromium-swarm.appspot.com/task?id=3ca8cec374c58f10 The task was killed, but luci-scheduler continued to report that it was running, which prevented it from scheduling new builds. I've manually aborted the job to allow next build to be scheduled, but IMHO the service should detect such killed builds and report them as aborted automatically.
,
Apr 4 2018
,
Apr 4 2018
it's not scheduler, it's buildbucket which is still reporting job as running -- actually, MILO's output is also weird -- it says "Pending" despite also showing some green steps:
,
Apr 4 2018
,
Apr 4 2018
,
Apr 4 2018
|
||||
►
Sign in to add a comment |
||||
Comment 1 by serg...@chromium.org
, Apr 4 2018