New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 816873 link

Starred by 6 users
Status: Duplicate
Owner: ----
Closed: Feb 2018
Cc:
█ kereliuk@chromium.org
rhalavati@chromium.org
chrome-trooper-bugs@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

Several builders have job pending for hours

Project Member Reported by hbos@chromium.org, Feb 27 2018 
Several builders have job pending for hours, with nothing in the current build

Examples:
https://ci.chromium.org/buildbot/tryserver.chromium.linux/fuchsia_arm64/
Last build 2018-02-27 3:51 AM (CET)

https://ci.chromium.org/buildbot/tryserver.chromium.linux/cast_shell_linux/
Last build 2018-02-27 3:56 AM (CET)

https://ci.chromium.org/buildbot/tryserver.chromium.linux/linux_chromium_tsan_rel_ng/
Last build 2018-02-27 4:18 AM (CET)

This CL has had these and more bots queued on the CQ for hours and the jobs never start:
https://chromium-review.googlesource.com/c/chromium/src/+/934182/3

Comment 1 by msramek@chromium.org, Feb 27 2018 

This is how the trybout output looks like on a CL:

Dry run: Try jobs failed on following builders:
  cast_shell_linux on master.tryserver.chromium.linux (JOB_TIMED_OUT, build has not started yet; builder either lacks capacity or does not exist (misspelled?))
  fuchsia_arm64 on master.tryserver.chromium.linux (JOB_TIMED_OUT, build has not started yet; builder either lacks capacity or does not exist (misspelled?))
  fuchsia_x64 on master.tryserver.chromium.linux (JOB_TIMED_OUT, build has not started yet; builder either lacks capacity or does not exist (misspelled?))
  linux_chromium_asan_rel_ng on master.tryserver.chromium.linux (JOB_TIMED_OUT, build has not started yet; builder either lacks capacity or does not exist (misspelled?))
  linux_chromium_headless_rel on master.tryserver.chromium.linux (JOB_TIMED_OUT, build has not started yet; builder either lacks capacity or does not exist (misspelled?))
  linux_chromium_ozone_compile_only_ng on master.tryserver.chromium.linux (JOB_TIMED_OUT, build has not started yet; builder either lacks capacity or does not exist (misspelled?))
  linux_chromium_tsan_rel_ng on master.tryserver.chromium.linux (JOB_TIMED_OUT, build has not started yet; builder either lacks capacity or does not exist (misspelled?))

Comment 2 by raphael....@intel.com, Feb 27 2018

Cc: kereliuk@chromium.org
+kereliuk, on ecosystem-infra rotation today.

Comment 4 by zhangtiff@chromium.org, Feb 27 2018

Mergedinto: 816817
Status: Duplicate (was: Available)
I believe this is caused by the same cause as a CQ outage earlier today.

Comment 5 by kereliuk@chromium.org, Feb 27 2018 

Currently looking into getting this back up and running
►

Sign in to add a comment