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

Issue 806969 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Mar 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: ----



Sign in to add a comment

"EXPIRED (lack of capacity)" Issue on Android Nexus5X WebView Perf

Project Member Reported by sheriff-...@appspot.gserviceaccount.com, Jan 29 2018

Issue description

Filed by sheriff-o-matic@appspot.gserviceaccount.com on behalf of sullivan@google.com

bot affinity 'build166-b1--device1', 'build166-b1--device2', 'build166-b1--device3', 'build166-b1--device4', 'build166-b1--device5', 'build166-b1--device6', 'build166-b1--device7' is broken on chromium.perf/Android Nexus5X WebView Perf, affecting 27 tests

Builders failed on: 
- Android Nexus5X WebView Perf: 
  https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus5X%20WebView%20Perf
- Android Nexus5X WebView Perf: 
  https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus5X%20WebView%20Perf

Lots of these tests are failing with "EXPIRED (lack of capacity)" in the logs:
https://logs.chromium.org/v/?s=chrome%2Fbb%2Fchromium.perf%2FAndroid_Nexus5X_WebView_Perf%2F1076%2F%2B%2Frecipes%2Fsteps%2Fblink_perf.css_on_Android%2F0%2Fstdout

Ned, any ideas how to triage? Is there a chart or something that would tell us a specific benchmark is taking longer?

 
Components: Infra>Client>Perf
Owner: oysteine@chromium.org
Oystein, as bot health sheriff, can you triage?
Status: Fixed (was: Available)
Looks like this recovered at some point.

Sign in to add a comment