New issue
Advanced search Search tips
Starred by 1 user
Status: Fixed
Owner:
Closed: Nov 20
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment
veyron_rialto-paladin failed at BuildImage staging due to package: chromeos-base/telemetry
Project Member Reported by shuqianz@chromium.org, Nov 14 Back to list
https://uberchromegw.corp.google.com/i/chromeos/builders/veyron_rialto-paladin/builds/6086

== Complete: job telemetry-0.0.1-r6 (0m15.1s) ===
Failed chromeos-base/telemetry-0.0.1-r6 (in 0m15.1s). Your build has failed.
Pending 3/104, [Time 16:44:12 | Elapsed 0m59.5s | Load 8.34 6.65 7.48]
Packages failed:
	chromeos-base/telemetry-0.0.1-r6
INFO    : Unmounting image from /mnt/host/source/src/build/images/veyron_rialto/R64-10125.0.0-rc3/stateful and /mnt/host/source/src/build/images/veyron_rialto/R64-10125.0.0-rc3/rootfs
Cleaning up /usr/local symlinks for /mnt/host/source/src/build/images/veyron_rialto/R64-10125.0.0-rc3/stateful/dev_image
An error occurred in your build so your latest output directory is invalid.
Running in non-interactive mode so deleting output directory.
Deleted /mnt/host/source/src/build/images/veyron_rialto/R64-10125.0.0-rc3
16:44:16: ERROR: 
return code: 1; command: /b/c/cbuild/repository/chromite/bin/cros_sdk 'PARALLEL_EMERGE_STATUS_FILE=/tmp/tmpxCwEMR' 'USE=chrome_internal' 'FEATURES=separatedebug' -- ./build_image '--board=veyron_rialto' --replace '--version=10125.0.0-rc3' '--builder_path=veyron_rialto-paladin/R64-10125.0.0-rc3' base test
cmd=['/b/c/cbuild/repository/chromite/bin/cros_sdk', 'PARALLEL_EMERGE_STATUS_FILE=/tmp/tmpxCwEMR', u'USE=chrome_internal', 'FEATURES=separatedebug', '--', './build_image', u'--board=veyron_rialto', '--replace', '--version=10125.0.0-rc3', u'--builder_path=veyron_rialto-paladin/R64-10125.0.0-rc3', u'base', u'test'], cwd=/b/c/cbuild/repository, extra env={'PARALLEL_EMERGE_STATUS_FILE': '/tmp/tmpxCwEMR', 'USE': u'chrome_internal', 'FEATURES': 'separatedebug'}
16:44:16: ERROR: Packages failed in ./build_image: chromeos-base/telemetry
16:44:16: INFO: Translating result Packages failed in ./build_image: chromeos-base/telemetry to fail.
 
Both build 6084 and 6086 exhibited the same failure. Looks like build_image may have failed due to running out of rootfs space:

  telemetry-0.0.1-r6: !!! [Errno 28] No space left on device
Cc: dgarr...@chromium.org nxia@chromium.org
Don, ningning, what do we usually do to fix the 'No space' issue?
Owner: benchan@chromium.org
Benchan@, as sheriff, can you find an owner of this? This seems like a product issue.
Owner: kumarniranjan@chromium.org
Status: Assigned
Looks like the chromeos-base/telemetry dependency is reintroduced indirectly due to https://chrome-internal-review.googlesource.com/c/chromeos/overlays/overlay-variant-veyron-rialto-private/+/500632, which dropped the "chromeless_tests" USE flag:

virtual/target-chromium-os-test-1-r54 (!chromeless_tests ? chromeos-base/telemetry)

Assigning to kumarniranjan@chromium.org to evaluate.
Are these tests running on the actual veyron_rialto devices, or on a VM? The actual devices in the test lab have 16GB of flash storage, so I don't expect them to get full. Is there a way to check how much space was available for the build?
Comment 8 by benchan@chromium.org, Nov 20 (4 days ago)
Status: Fixed
I believe the issue has been resolved as veyron_rialto-paladin has been passing

The original CL was reverted: https://chrome-internal-review.googlesource.com/c/chromeos/overlays/overlay-variant-veyron-rialto-private/+/504652 

A revised CL has been landed: https://chrome-internal-review.googlesource.com/c/chromeos/overlays/overlay-variant-veyron-rialto-private/+/506613
Sign in to add a comment