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

Issue 699348 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: Oct 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Swarming collect takes 8 hours

Project Member Reported by martiniss@chromium.org, Mar 8 2017

Issue description

https://luci-milo.appspot.com/buildbot/chromium.perf/Mac%20Pro%2010.11%20Perf/693 is the relevant build. In particular, the "jitter.reference" collect step takes 8 hours. https://build.chromium.org/p/chromium.perf/builders/Mac%20Pro%2010.11%20Perf/builds/693/steps/jitter.reference%20on%20ATI%20GPU%20on%20Mac%20on%20Mac-10.11

It's weird that it took 8 hours to timeout. All the jobs have a timeout of 6 hours in that build.

I saw this in the step log:

7947 2017-03-07 19:57:07.479 E: retrieve_results(https://chromium-swarm.appspot.com) timed out on attempt 1934

Is that relevant?

Not sure what the best component for this is.
 
Owner: mar...@chromium.org
Status: Assigned (was: Available)
https://chromium-swarm.appspot.com/task?id=34c147a7ab0a5810&refresh=10&request_detail=true&show_raw=1

Duration: 2d 8h 33m 37s
Execution timeout: 2h

So there's *something* wrong with this task. Sorry for the inconvenience, I'll take a look if I can find out what happened from what I can harvest.

Comment 2 by mar...@chromium.org, Oct 30 2017

Status: Fixed (was: Assigned)
The bug was found and fixed. This was a problem with memcache incoherency in https://chromium-review.googlesource.com/671066

Sign in to add a comment