New issue
Advanced search Search tips

Issue 643134 link

Starred by 1 user
Status: Duplicate
Merged: issue 636405
Owner:
jochen@chromium.org
Closed: Sep 2016
Cc:
eyaich@chromium.org
skyos...@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Android Nexus5 Perf (3) failing on v8.todomvc.reference

Project Member Reported by picksi@chromium.org, Sep 1 2016 
bot link: https://uberchromegw.corp.google.com/i/chromium.perf/builders/Android%20Nexus5%20Perf%20%283%29?numbuilds=200


v8.todomvc test has always been flaky (failing 1 in 4 times on average), but since Aug 20th (build #2959) it has failed with every build. There is no obviously related CL that landed with #2959, so I wonder if there was an infrastructure change?

Jochen, Emily, any ideas as to what might have happened here?

Comment 1 by jochen@chromium.org, Sep 1 2016

Mergedinto: 636405
Status: Duplicate (was: Untriaged)
we don't get idle time anymore on the nexus 5 bots - any insight into why would be more than welcome...

Comment 2 by picksi@chromium.org, Sep 1 2016

Cc: skyos...@chromium.org
Sami, do you have any insight into why idle time might have disappeared?

I see a todomvc CL: https://codereview.chromium.org/2274933002, which adds logging. This lands at the same time that the Nexus6 bot turned red (https://uberchromegw.corp.google.com/i/chromium.perf/builders/Android%20Nexus6%20Perf%20%283%29/builds/3176).

Would extra logging (which I guess could be slow, relatively speaking) eat up all the idle time?
►

Sign in to add a comment