Buildroots being heavily wiped. |
|||||||
Issue descriptionWhile looking into why some builds appear to be taking a long time to start, I found that InitialSync is often taking up 45 minutes, and that the Clean step before it is seeing "Unknown layout: Wiping buildroot". https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8943179840228975120 This graph shows how often we see that error, which has suddenly spiked. http://shortn/_TS64ELy8EC PS: That error is only expected on brand new builders, or when we explicitly change the build directory layout, which hasn't happened.
,
Jun 20 2018
,
Jun 20 2018
PS: This behavior could cause a huge spike in GoB usage.
,
Jun 20 2018
,
Jun 20 2018
Is this related to crbug.com/854278 ?
,
Jun 20 2018
I don't think it's related to candy provision problems. It seems super related to https://crbug.com/854652 , but that the timing doesn't match up.
,
Jul 25
,
Jul 30
Is this still happening? I'm going to close it for now, please re-open if it's not just a side effect of crbug.com/854652 .
,
Jul 31
It's still happening more than I would expect. Looks like 12 times an hour. http://shortn/_Tzrks8JRWN This is expected when a new builder is brought up (not in weeks), we update the build directory layout (hasn't happened in about a year), or the 'cbuild' named cache is wiped between builds. Maybe our named cache is being wiped? Each time it happens, the initial sync becomes very slow. ~ 30 minutes added to the build time.
,
Aug 1
,
Aug 1
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by dgarr...@chromium.org
, Jun 20 2018