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

Issue 642083 link

Starred by 1 user
Status: Fixed
Owner: ----
Closed: Oct 2016
Cc:
█ nednguyen@chromium.org
dtu@chromium.org
sullivan@chromium.org
█ aiolos@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug-Regression



Sign in to add a comment

several builders on chromium.perf cycle time has increased dramatically

Project Member Reported by martiniss@chromium.org, Aug 29 2016 
https://uberchromegw.corp.google.com/i/chromium.perf/builders/Android%20Nexus5%20Perf%20%281%29
https://uberchromegw.corp.google.com/i/chromium.perf/builders/Android%20Nexus7v2%20Perf%20%281%29
https://uberchromegw.corp.google.com/i/chromium.perf/builders/Android%20Nexus7v2%20Perf%20%282%29
https://uberchromegw.corp.google.com/i/chromium.perf/builders/Android%20Nexus5%20Perf%20%282%29
all these builders are affected. They started to fail a fairly random selection of tests as well. The last couple builds for at least https://uberchromegw.corp.google.com/i/chromium.perf/builders/Android%20Nexus5%20Perf%20%282%29 have taken about 10 hours...

jbudorick said that it looks like this happened because of the new catapult roll? Non perf android infra have been having issues this morning, although I think it could be because of a different issue.

aiolos@ bumped the reference revision last friday, I thought.

Comment 1 by sullivan@chromium.org, Aug 29 2016

Cc: dtu@chromium.org nednguyen@chromium.org
Components: Tests>Telemetry
+nednguyen, dtu

This could definitely be related to the longer cycle times on telemetry CQ.

Dave, is there a good way to know what's taking longer on the perf waterfall (from firefighter or the scripts checked into catapult?)

Ned, same question about CQ, any ideas how to figure out which roll it started with and which tests take longer?

Comment 2 by dtu@chromium.org, Aug 29 2016 

The Android reference build roll was bad.

The builds are taking longer because a lot of the reference runs are failing, and they implicitly retry on failure.

Comment 3 by dtu@chromium.org, Aug 29 2016 

BTW this is the same cause as most of the other Android bot failures.
E.g. the "list perf tests" failure on Android One.
https://build.chromium.org/p/chromium.perf/builders/Android%20One%20Perf%20%281%29/builds/3827

Comment 4 by zh...@chromium.org, Oct 3 2016 

Ping. Is this still a problem?

Comment 5 by martiniss@chromium.org, Oct 3 2016

Status: Fixed (was: Available)
I think this got solved.
►

Sign in to add a comment