mac_pro_perf_bisect needs clobber |
|||||||||
Issue descriptionhttps://luci-logdog.appspot.com/v/?s=chrome%2Fbb%2Ftryserver.chromium.perf%2Fmac_pro_perf_bisect%2F155%2F%2B%2Frecipes%2Fsteps%2Fbot_update%2F0%2Fstdout It's trying to download ~21 GB of flash symbols (why?) and fails because there's no space left on disk.
,
Apr 25 2017
,
Apr 26 2017
,
Apr 26 2017
Any idea if we can just null out that entry in the gclient spec? Do we need that on the tester, or should the zip contain everything we need?
,
Apr 26 2017
,
Apr 26 2017
,
Apr 26 2017
I tried clobbering via the buildbot menu, 2 of the builders seem to be chugging along but the 3rd I guess didn't even have enough space get more than a few steps in. +pschmidt who's helped in the past, how do I manually go and clobber these?
,
Apr 26 2017
I use the big hammer approach: Log onto the slave and rm -rf /b/c
,
Apr 27 2017
Ok I used pschmidt's big hammer approach, let's see if that last bot works now.
,
May 4 2017
,
May 25 2017
Think clobbering these doesn't help anymore, we may have to just bring them offline until Pinpoint is ready.
,
May 25 2017
+Ned, Stephen: is this the same root cause as bug 661661 ? Would fixing removal of breakpad logs help?
,
May 25 2017
Swarming have an automatic solution for clean up builder (see issue 724570 ). Short term fix is probably manually remove whichever files haven't been touched there. Longer term fix is probably swarming (pinpoint)
,
May 25 2017
Been doing just clobbering the whole bot and letting it resync, which used to buy us a week or 2, and now we're running out of disk space again on the first run. Seems like either we get it to sync fewer things (like could we skip the flash symbols mentioned in the first post?), otherwise seems like we need to wait on Pinpoint.
,
Oct 4
Waited long enough, we're using Pinpoint now. |
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by efoo@chromium.org
, Apr 25 2017Components: -Infra Speed>Bisection