New issue
Advanced search Search tips

Issue 830266 link

Starred by 1 user
Status: Fixed
Owner:
qyears...@chromium.org
Closed: Apr 2018
Cc:
jchin...@chromium.org
tkent@chromium.org
hinoka@chromium.org
mar...@chromium.org
mac-bugs-priority@chromium.org
chrome-trooper-bugs@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 1
Type: Bug



Sign in to add a comment

Mac 10.{11,12} Tests steps failing with "not enough capacity"

Project Member Reported by qyears...@chromium.org, Apr 8 2018 
This started happening after the Great Blink mv, on most but not all steps for these two builders.

Example build: https://ci.chromium.org/buildbot/chromium.mac/Mac10.12%20Tests/11905

Example log excerpt:

...
+------------------------------------------------------------------------+
| Shard 0  https://chromium-swarm.appspot.com/user/task/3cbd5cbb49452210 |
+------------------------------------------------------------------------+
+------------------------------------------------------------------------+
| End of shard 0                                                         |
|  Pending: 3608.3s  EXPIRED (lack of capacity)                          |
+------------------------------------------------------------------------+
...
There wasn't enough capacity to run your test

Comment 1 by qyears...@chromium.org, Apr 8 2018

Cc: -qyears...@chromium.org
Owner: qyears...@chromium.org
Status: Assigned (was: Available)
Recent build links:
https://ci.chromium.org/buildbot/chromium.mac/Mac10.11%20Tests/
https://ci.chromium.org/buildbot/chromium.mac/Mac10.12%20Tests/

These started failing around the time of
https://chromium.googlesource.com/chromium/src/+/69c0f6d7de7073ed86bb24ab4addc9eb0decbacf (a follow-up change for the Great Blink mv), but may not necessarily be directly caused by that particular change.

Comment 2 by qyears...@chromium.org, Apr 8 2018

Cc: mar...@chromium.org jchin...@chromium.org hinoka@chromium.org
It seems that many of the bots that could run these task are dead:
https://chromium-swarm.appspot.com/botlist?c=id&c=os&c=task&c=status&f=gpu%3Anone&f=os%3AMac-10.12&f=cpu%3Ax86-64&f=pool%3AChrome&l=100&s=id%3Aasc

Comment 3 by qyears...@chromium.org, Apr 8 2018 

Power-cycled the dead bots.

Comment 4 by qyears...@chromium.org, Apr 8 2018

Components: -Infra
Mac10.12 just had a green build, but not Mac10.11; I just realized that this is because I power-cycled the dead Mac10.12 bots but not Mac10.11 ones. Will do that now.

Comment 5 by qyears...@chromium.org, Apr 8 2018

Status: Fixed (was: Assigned)
Mac10.11 is now not failing in this way anymore, closing this bug.
►

Sign in to add a comment