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

Issue 714960 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: Oct 4
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug

Blocking:
issue 715056
issue 715561



Sign in to add a comment

mac_pro_perf_bisect needs clobber

Project Member Reported by sunn...@chromium.org, Apr 25 2017

Issue description

https://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.
 

Comment 1 by efoo@chromium.org, Apr 25 2017

Cc: sullivan@chromium.org
Components: -Infra Speed>Bisection
Moving to Speed Ops Bisection. CC'ed Annie to triage. 
Owner: simonhatch@chromium.org
Blocking: 715561
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?
Blocking: 715056
Cc: simonhatch@chromium.org
 Issue 715475  has been merged into this issue.
Cc: pschmidt@chromium.org
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?

Comment 8 by pschm...@google.com, Apr 26 2017

I use the big hammer approach:   Log onto the slave and rm -rf /b/c
Ok I used pschmidt's big hammer approach, let's see if that last bot works now.
Status: Assigned (was: Untriaged)
Cc: dtu@chromium.org
Think clobbering these doesn't help anymore, we may have to just bring them offline until Pinpoint is ready.
Cc: nedngu...@google.com martiniss@chromium.org
+Ned, Stephen: is this the same root cause as  bug 661661 ? Would fixing removal of breakpad logs help?
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)
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.
Status: Fixed (was: Assigned)
Waited long enough, we're using Pinpoint now.

Sign in to add a comment