Commit Queue is showing try jobs as "grey" (not started) for unusually long periods of time |
||||||
Issue descriptionWhen triggering a CQ job, normally the "grey" period would last for only a few seconds, before being replaced with "yellow" in-progress mode. Currently some active jobs are being run for 20 minutes or more without being switched from grey to yellow status. I believe this is making the CQ time out and fail on correct CL. An odd thing is often the grey links are clickable and they take you to the bot runs, sometimes which complete successfully but remain as grey. Noticed this on both the ANGLE and Chromium CQs, possibly affecting all infra, so marking Pri-0. Please consider downgrading priority if this is appropriate. See attached screenshot and links https://chromium-review.googlesource.com/c/chromium/src/+/1014002 https://chromium-cq-status.appspot.com/v2/patch-status/chromium-review.googlesource.com/1014002/1 https://chromium-review.googlesource.com/c/angle/angle/+/1011680 https://chromium-cq-status.appspot.com/v2/patch-status/chromium-review.googlesource.com/1011680/10
,
Apr 16 2018
Seeing the same thing with my CL: https://chromium-cq-status.appspot.com/v2/patch-status/chromium-review.googlesource.com/998213/25
,
Apr 16 2018
Andrii, Nodir: Do you know if this is related to the issue about removing a builder without removing it from cq.cfg (https://crrev.com/c/1011216), or is this a separate issue?
,
Apr 16 2018
This might only be LUCI bots.
,
Apr 16 2018
,
Apr 16 2018
,
Apr 16 2018
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by raphael....@intel.com
, Apr 16 2018