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

Issue 777874 link

Starred by 2 users

Issue metadata

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



Sign in to add a comment

M63: Target image has run out of space for Reef platform boards

Project Member Reported by josa...@chromium.org, Oct 24 2017

Issue description

Here is log snippet:
446676992 opt/google/containers/android/system.raw.img
ERROR   : Target image has run out of space:
ERROR   : Filesystem     1M-blocks  Used Available Use% Mounted on
ERROR   : /dev/loop0          1723  1723         0 100% /mnt/host/source/src/build/images/pyro/R63-10032.14.0/rootfs
INFO    : Unmounting image from /mnt/host/source/src/build/images/pyro/R63-10032.14.0/stateful and /mnt/host/source/src/build/images/pyro/R63-10032.14.0/rootfs
Cleaning up /usr/local symlinks for /mnt/host/source/src/build/images/pyro/R63-10032.14.0/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/pyro/R63-10032.14.0
03:54:09: ERROR: 
return code: 1; command: /b/c/cbuild/repository/chromite/bin/cros_sdk 'PARALLEL_EMERGE_STATUS_FILE=/tmp/tmpAho49b' 'USE=-cros-debug chrome_internal afdo_use' 'FEATURES=separatedebug' 'CHROME_ORIGIN=LOCAL_SOURCE' -- ./build_image '--board=pyro' --replace '--version=10032.14.0' '--builder_path=pyro-release/R63-10032.14.0' base test
cmd=['/b/c/cbuild/repository/chromite/bin/cros_sdk', 'PARALLEL_EMERGE_STATUS_FILE=/tmp/tmpAho49b', u'USE=-cros-debug chrome_internal afdo_use', 'FEATURES=separatedebug', 'CHROME_ORIGIN=LOCAL_SOURCE', '--', './build_image', u'--board=pyro', '--replace', '--version=10032.14.0', u'--builder_path=pyro-release/R63-10032.14.0', 'base', 'test'], cwd=/b/c/cbuild/repository, extra env={'PARALLEL_EMERGE_STATUS_FILE': '/tmp/tmpAho49b', 'USE': u'-cros-debug chrome_internal afdo_use', 'FEATURES': 'separatedebug', 'CHROME_ORIGIN': 'LOCAL_SOURCE'}

Full log: https://uberchromegw.corp.google.com/i/chromeos_release/builders/pyro-release%20release-R63-10032.B/builds/12/steps/BuildImage%20%5Bafdo_use%5D/logs/stdio
 
Cc: snanda@chromium.org
Components: OS>Installer
Labels: -Hardware-Lab
Owner: ----
I'm not sure of the right labels/component but this isn't an
Infra problem.  It's a product problem.  Basically, the root
partition in reef is too small for all the software we're trying
to install on it.

Cc: norvez@chromium.org

Comment 3 by norvez@chromium.org, Oct 24 2017

Hmm, it looks like ag/3075149 is not in M-63, I'll merge it. That should reduce the size of the vendor image and give yield just enough space in the root partition during the build.

Comment 4 by norvez@chromium.org, Oct 24 2017

BTW, I just filed  crbug.com/777907  to get a better error message in that case, we keep misdiagnosing that out-of-space error.

Comment 5 by norvez@chromium.org, Oct 24 2017

Owner: norvez@chromium.org
Status: Started (was: Available)
ag/3075149 has been merged to M-63 as ag/3118075.

Comment 6 by norvez@chromium.org, Oct 25 2017

Status: Fixed (was: Started)
The reef PFQ on R63 is now passing: https://luci-milo.appspot.com/buildbot/chromeos_release/reef-android-nyc-pre-flight-branch%20release-R63-10032.B/59
The -release builders should turn green on the next run.

Comment 7 by norvez@chromium.org, Oct 27 2017

Cc: gurcheta...@chromium.org
Status: Started (was: Fixed)
The builds still occasionally run out of space. Gurchetan is going to merge https://chromium-review.googlesource.com/c/chromiumos/overlays/chromiumos-overlay/+/716867 to M-53, that should save ~40MB

Comment 8 by norvez@chromium.org, Oct 27 2017

Owner: gurcheta...@chromium.org
Project Member

Comment 9 by bugdroid1@chromium.org, Oct 27 2017

Labels: merge-merged-release-R63-10032.B
The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/0b859d567c5d092f0a8ff8f5561e8f2cf98b0654

commit 0b859d567c5d092f0a8ff8f5561e8f2cf98b0654
Author: Gurchetan Singh <gurchetansingh@chromium.org>
Date: Fri Oct 27 16:23:02 2017

media-libs/mesa: enable swrast drivers when USE flag is set (reland)

With CL:704594 landed, we can stop building unnecessary drivers for
every board. Note the 9999 ebuild already has this change.

BUG= chromium:765364 
BUG= chromium:777874 
TEST=emerge-cave doesn't build swrast_dri.so or kms_swrast_dri.so
     emerge-betty doesn't build i965.so

Change-Id: Ia4cb6318185036f5057334925a52a37c5e03cc9d
Reviewed-on: https://chromium-review.googlesource.com/716867
Commit-Ready: Gurchetan Singh <gurchetansingh@chromium.org>
Tested-by: Gurchetan Singh <gurchetansingh@chromium.org>
Reviewed-by: Ilja H. Friedel <ihf@chromium.org>
Reviewed-by: Stéphane Marchesin <marcheu@chromium.org>
(cherry picked from commit a4c7e3d5918d9e8ab694cb0742867a04250d52c8)
Reviewed-on: https://chromium-review.googlesource.com/741089
Commit-Queue: Nicolas Norvez <norvez@chromium.org>
Tested-by: Nicolas Norvez <norvez@chromium.org>
Reviewed-by: Gurchetan Singh <gurchetansingh@chromium.org>

[rename] https://crrev.com/0b859d567c5d092f0a8ff8f5561e8f2cf98b0654/media-libs/mesa/mesa-17.1.1-r11.ebuild
[modify] https://crrev.com/0b859d567c5d092f0a8ff8f5561e8f2cf98b0654/media-libs/mesa/mesa-17.1.1.ebuild

Status: Fixed (was: Started)

Sign in to add a comment