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

Issue 664163 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Nov 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: ----



Sign in to add a comment

List Perf Tests failing on chromium.perf/Win 10 High-DPI Perf (4)

Project Member Reported by sullivan@chromium.org, Nov 10 2016

Issue description

Link to buildbot status page:
https://uberchromegw.corp.google.com/i/chromium.perf/builders/Win%2010%20High-DPI%20Perf%20%284%29
https://uberchromegw.corp.google.com/i/chromium.perf/builders/Win%2010%20High-DPI%20Perf%20%284%29/builds/353

I don't see anything useful in the output. But it doesn't seem to be a recipe issue, since it's only purple on the one bot. Can the trooper take a look?
 

Comment 1 by aga...@chromium.org, Nov 10 2016

Cc: katthomas@chromium.org andyb...@chromium.org
Owner: martiniss@chromium.org
Status: Assigned (was: Untriaged)
Damn, I was really hoping this would be identical to the List Perf Tests failure from yesterday (chromium:663759), but this looks like a hang instead of a corrupt checkout.

The problem is that I (nor any other infra person, as far as I know) has any idea what the List Perf Tests step does. I'm going to assign to martiniss@, who might/should know the most, and cc andybons@, as shared responsibility for a script like this is a thing he should be aware of.

Finally, I'm going to CC katthomas@ just as an FYI of another failure mode, because this build turned purple (infra failure) because it was killed by the buildbot master after 2400s of no logging output from the slave. This is why we need per-step timeouts, so that the recipe can kill steps and mark them red before the master kills the whole build and marks it purple. martiniss@, please also add a timeout to this step during your investigation.

Comment 2 by aga...@chromium.org, Nov 10 2016

In the mean time, I've moved the b/build/slave/buildername/build directory to .../build.investigate, and also b/c/b/buildername to b/c/b/buildername.investigate to effectively clobber the bot and leave the directory behind for investigation. Hopefully the "clobber" will help.

Comment 3 by zh...@chromium.org, Nov 15 2016

Status: Fixed (was: Assigned)
Seems fixed? reopen if needed.
Labels: Infra-Failures
Labels: Hotlist-Infra-Failures

Sign in to add a comment