LUCI Schedule double scheduling a build? |
||
Issue descriptionThis scheduler: https://luci-scheduler.appspot.com/jobs/chromeos/amd64-generic-tot-chromium-pfq-informational Is currently running two active builds: Build A: https://luci-scheduler.appspot.com/jobs/chromeos/amd64-generic-tot-chromium-pfq-informational/9110377558185414384 https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8944947495923138096 Build B: https://luci-scheduler.appspot.com/jobs/chromeos/amd64-generic-tot-chromium-pfq-informational/9110312412330160128 https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8944882350077720256 When I check the buildbucket API, both buildbucket ids report a status of STARTED. The older build appears to be hung, and I'm expected it to be killed when the buildbucket 24 hour timeout is hit. The LUCI scheduler configuration was updated in the middle of this, possibly including the configuration for this job.
,
Jun 1 2018
From my PoV, this is WontFix in scheduler. Retrying 404s isn't really good.
,
Jun 1 2018
Are the builds in question really still running, or are they lying to the UI? If they are going to stick around in status STARTED forever, that would be bad. If they will be cleaned up after 24 hours, no big deal.
,
Jun 1 2018
PS: I agree about the scheduler priority.
,
Jun 2 2018
This build https://ci.chromium.org/p/chromeos/builds/b8944947495923138096 is still running. Buildbucket certainly thinks so, and so does swarming https://chrome-swarming.appspot.com/task?id=3dd29a51c5648c10&refresh=10&show_raw=1&wide_logs=true |
||
►
Sign in to add a comment |
||
Comment 1 by vadimsh@chromium.org
, Jun 1 2018