veyron_rialto-paladin CQ BuildImage failing: out of space |
||||||
Issue descriptionhttps://uberchromegw.corp.google.com/i/chromeos/builders/veyron_rialto-paladin/builds/1849 https://uberchromegw.corp.google.com/i/chromeos/builders/veyron_rialto-paladin/builds/1849/steps/BuildImage/logs/stdio Out of space errors when trying to build packages: IOError: [Errno 28] No space left on device ERROR : Target image has run out of space: ERROR : Filesystem 1M-blocks Used Available Use% Mounted on ERROR : /dev/loop0 886 886 0 100% /mnt/host/source/src/build/images/veyron_rialto/R55-8754.0.0-rc1/rootfs INFO : Unmounting image from /mnt/host/source/src/build/images/veyron_rialto/R55-8754.0.0-rc1/stateful and /mnt/host/source/src/build/images/veyron_rialto/R55-8754.0.0-rc1/rootfs In https://bugs.chromium.org/p/chromium/issues/detail?id=591401 vapier@ suggested to look at this dashboard: https://chromeperf.appspot.com/report?sid=d2c8d8b3c8780bb331d2aaff94189c36d7a2dceb373903b03424f9982282032f under build_RootFilesystemSize -> $board -> bytes_rootfs_prod, but I don't see veyron_rialto in there. I don't see this issue in previous builds -- only #1849. #1850 is still building: https://uberchromegw.corp.google.com/i/chromeos/builders/veyron_rialto-paladin/builds/1850
,
Aug 30 2016
,
Aug 30 2016
rialto isn't listed because you guys disabled the test ;)
src/private-overlays/overlay-variant-veyron-rialto-private/make.conf:
USE="${USE} -tests_build_RootFilesystemSize"
,
Aug 30 2016
,
Aug 30 2016
This was broken by https://chrome-internal-review.googlesource.com/#/c/274317/ so this was a legitimate Paladin failure.
,
Aug 31 2016
As https://chrome-internal-review.googlesource.com/#/c/274317/ was abandoned due to the problem being correctly detected pre submit, is there anything left to do here or can the this bug be closed? @3 yes rialto has too many test disabled, most recently this was due to a chain of test infras problem causing tests to fail and the wrong ones being hit in the game of whack-a-mole. I sent https://chrome-internal-review.googlesource.com/#/c/282796/ to undo that.
,
Jul 17 2017
ChromeOS Infra P1 Bugscrub. P1 Bugs in this component should be important enough to get weekly status updates. Is this already fixed? -> Fixed Is this no longer relevant? -> Archived or WontFix Is this not a P1, based on go/chromeos-infra-bug-slo rubric? -> lower priority. Is this a Feature Request rather than a bug? Type -> Feature Is this missing important information or scope needed to decide how to proceed? -> Ask question on bug, possibly reassign. Does this bug have the wrong owner? -> reassign. Bugs that remain in this state next week will be downgraded to P2.
,
Jul 24 2017
ChromeOS Infra P1 Bugscrub. Issue untouched in a week after previous message. Downgrading to P2.
,
May 15 2018
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by dgarr...@chromium.org
, Aug 30 2016