glados-release failing InitSdk (build106-m2) |
||||||||||||
Issue descriptionThis failure is happening consistently on the glados release builder: https://uberchromegw.corp.google.com/i/chromeos/builders/glados-release/builds/11/steps/InitSDK/logs/stdio STEP_TEXT: 2016.05.04.091854 17:30:45: NOTICE: Downloading SDK tarball... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 2 1408M 2 36.8M 0 0 48.8M 0 0:00:28 --:--:-- 0:00:28 48.9M 17 1408M 17 240M 0 0 135M 0 0:00:10 0:00:01 0:00:09 135M 35 1408M 35 496M 0 0 180M 0 0:00:07 0:00:02 0:00:05 180M 52 1408M 52 736M 0 0 196M 0 0:00:07 0:00:03 0:00:04 196M 76 1408M 76 1081M 0 0 227M 0 0:00:06 0:00:04 0:00:02 227M 100 1408M 100 1408M 0 0 247M 0 0:00:05 0:00:05 --:--:-- 277M 17:30:51: NOTICE: Creating chroot. This may take a few minutes... make_chroot.sh: Building with a non-empty USE: -cros-debug chrome_internal This modifies the expected behaviour and can fail. INFO cros_sdk:make_chroot: Unpacking stage3... tar: This does not look like a tar archive tar: Exiting with failure status due to previous errors
,
May 10 2016
Just by the want, I do NOT replicate this with a normal local glados build.
,
May 10 2016
I also don't see this warning: make_chroot.sh: Building with a non-empty USE: -cros-debug chrome_internal
,
May 10 2016
Passing to the deputy to find an owner. This is probably an infra problem, but I don't know enough about the relevant bits to deal with it.
,
May 10 2016
+Mike, can you take a look?
,
May 10 2016
the make_chroot.sh/USE warning is normal when cbuildbot is active for release configs last time this kind of error came up, the bot itself was seeing hardware/system failures. you should ssh into it (build106-m2) and check dmesg to see if there's anything suspicious. also try clobbering the rootdir that it uses. i think any build deputy should have access to these boxes.
,
May 11 2016
I don't see anything scary in dmesg, though this builder is set to reboot after every build. We could ask for a builder swap to be sure.
,
May 11 2016
Before doing builder swap, you should probably ask for it to be reimaged. If you're going to do that, punt this ticket to labs.
,
May 11 2016
,
May 12 2016
Passing to labs to request that builder 106-m2 be reimaged.
,
May 12 2016
,
May 12 2016
,
May 12 2016
Doing this now. It will take a little while as I'm taking the opportunity to update firmware on this old r720
,
May 12 2016
Thanks!
,
May 13 2016
This was completed yesterday.
,
May 13 2016
And it fixed the build problem.
,
May 23 2016
Bulk verified
,
May 23 2016
bulk verified |
||||||||||||
►
Sign in to add a comment |
||||||||||||
Comment 1 by dgarr...@chromium.org
, May 10 2016