Bisect failing due to lack of space on drive |
||||
Issue descriptionI saw this on one bisect (see blocking). https://luci-logdog.appspot.com/v/?s=chrome%2Fbb%2Ftryserver.chromium.perf%2Fmac_pro_perf_bisect%2F121%2F%2B%2Frecipes%2Fsteps%2Fresolving_hash_4a385fea357701f615577d64473706d36db87127%2F0%2Fstdout Traceback (most recent call last): File "/b/depot_tools/git_footers.py", line 200, in <module> sys.exit(main(sys.argv[1:])) File "/b/depot_tools/git_footers.py", line 181, in main print '%s@{#%s}' % (pos[0], pos[1] or '?') IOError: [Errno 28] No space left on device step returned non-zero exit code: 1
,
Apr 20 2017
An fyi there are MacBookAir7,1 third party ssd replacement options out there.
,
Apr 21 2017
How do I clobber this to get it going for now?
,
Apr 21 2017
Just clobbered the 3 bots that host mac_pro_perf_bisect. Note these are actually macbook air's. See https://bugs.chromium.org/p/chromium/issues/detail?id=710239#c5
,
Apr 21 2017
That seems bad, I'll find out how to switch those.
,
May 15 2017
Issue 722397 has been merged into this issue.
,
May 15 2017
Removing from the trooper queue (bot issues are resolved?). Please file a specific trooper bug if you need trooper help here.
,
Aug 16 2017
,
Oct 4
|
||||
►
Sign in to add a comment |
||||
Comment 1 by alexclarke@chromium.org
, Apr 20 2017