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

Issue 727607 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 727681
Owner: ----
Closed: May 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug-Regression

Blocking:
issue 727681



Sign in to add a comment

"Deterministic Linux" bot always redownloads everything from google storage during runhooks (causing flaky failures)

Project Member Reported by kjellander@chromium.org, May 30 2017

Issue description

When I was investigating flaky 'gclient runhooks' failures for the "Deterministic Linux" bot (bug 727559) I found that some of the failures were due to inability to download from Google storage.

Example: https://build.chromium.org/p/chromium.linux/builders/Deterministic%20Linux/builds/3173

Somehow this bot (only) always downloads everything during 'gclient runhooks', no matter if it was done in the previous build. I know it's a clobber bot that wipes everything in out/Release but the files in question are not located there so I don't know what's going on there.

One of two things must be happening here:
1) The VM is reimaged between each build - seems unlikely but I don't know how to verify that.
2) A completely new checkout is created for each build. I don't know why it would do that? I'm unable to see anything special in the recipe [1] except the clobber steps for out/Release

[1]: https://cs.chromium.org/chromium/build/scripts/slave/recipes/swarming/deterministic_build.py



 
Cc: phajdan@google.com
Looks like the builder has been converted to remote_run, and is using a custom recipe.

To keep the checkout directory between builds, please consider using logic from (or similar to) https://cs.chromium.org/chromium/build/scripts/slave/recipe_modules/chromium_checkout/api.py .
Blocking: 727681
Mergedinto: 727681
Status: Duplicate (was: Untriaged)

Sign in to add a comment