New issue
Advanced search Search tips

Issue 768017 link

Starred by 1 user
Status: Fixed
Owner:
jo...@chromium.org
Closed: Sep 2017
Cc:
martiniss@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: ----



Sign in to add a comment

bot affinity 'build131-b1' is broken on chromium.perf/Mac Pro 10.11 Perf, affecting 26 tests

Project Member Reported by simonhatch@chromium.org, Sep 22 2017 
bot affinity 'build131-b1' is broken on chromium.perf/Mac Pro 10.11 Perf, affecting 26 tests

Builders failed on: 
- Mac Pro 10.11 Perf: 
  https://build.chromium.org/p/chromium.perf/builders/Mac%20Pro%2010.11%20Perf


Seem to be seeing "shard #0 expired, not enough capacity" on some tests, +martiniss@ how do I find out which test is pushing this over the limit?

Comment 1 by martiniss@chromium.org, Sep 22 2017

Components: Infra>Labs
Labels: Pri-3
Owner: vhang@chromium.org
Status: Assigned (was: Available)
That bot is broken completely for that builder. You can tell this because in https://build.chromium.org/p/chromium.perf/builders/Mac%20Pro%2010.11%20Perf/builds/1504, if you Ctrl-F for 'build131-b1', every task with that as the bot id is expired, which means the bot wasn't able to run any tasks.

I'll re-assign this to vince to fix the bot. The whole b-lab is having issues though, so it might take a bit to fix it.

Comment 2 by jo...@google.com, Sep 22 2017

Owner: jo...@chromium.org

Comment 3 by jo...@chromium.org, Sep 23 2017

Status: Fixed (was: Assigned)
Battor had no light indications, and the bot was locked up. Reset both, and looking better as of now. Thanks.
►

Sign in to add a comment