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

Issue 628494 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Jul 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

chromeos-bootimage build failures in canary builds

Project Member Reported by semenzato@chromium.org, Jul 15 2016

Issue description

At least two canary builders failed with a similar error.  (Stefan can you help with this?  Thanks!)

https://uberchromegw.corp.google.com/i/chromeos/builders/peach_pi-release/builds/608/steps/BuildPackages%20%5Bafdo_use%5D/logs/stdio
https://uberchromegw.corp.google.com/i/chromeos/builders/jecht-release/builds/208/steps/BuildPackages%20%5Bafdo_use%5D/logs/stdio

peach_pi:

chromeos-bootimage-0.0.2-r1091: Creating GBB...
chromeos-bootimage-0.0.2-r1091:                
chromeos-bootimage-0.0.2-r1091: Command failed: /usr/bin/gbb_utility -s --hwid=PIT TEST A-A 7848 --rootkey=/build/peach_pi/usr/share/vboot/devkeys/root_key.vbpubk --recoverykey=/build/peach_pi/usr/share/vboot/devkeys/recovery_key.vbpubk --flags=57 --bmpfv=/build/peach_pi/firmware/bmpblk.bin gbb.bin
chromeos-bootimage-0.0.2-r1091: ERROR: Unable to open /build/peach_pi/firmware/bmpblk.bin for reading: No such file or directory
chromeos-bootimage-0.0.2-r1091:  - import root_key from /build/peach_pi/usr/share/vboot/devkeys/root_key.vbpubk: success
chromeos-bootimage-0.0.2-r1091:  - import recovery_key from /build/peach_pi/usr/share/vboot/devkeys/recovery_key.vbpubk: success
chromeos-bootimage-0.0.2-r1091: 
chromeos-bootimage-0.0.2-r1091: 
chromeos-bootimage-0.0.2-r1091:                
chromeos-bootimage-0.0.2-r1091:  * ERROR: sys-boot/chromeos-bootimage-0.0.2-r1091::chromiumos failed (compile phase):
chromeos-bootimage-0.0.2-r1091:  *   failed to build RO image:  --add-blob cros-splash /mnt/host/source/src/third_party/chromiumos-overlay/sys-boot/chromeos-bootimage/files/cros_splash_blob.bin --board peach_pi --key /build/peach_pi/usr/share/vboot/devkeys --bmpblk /build/peach_pi/firmware/bmpblk.bin --ecro /build/peach_pi/firmware/ec.RO.bin --ec /build/peach_pi/firmware/ec.RW.bin -D --bl1=/build/peach_pi/firmware/u-boot.bl1.bin --bl2=/build/peach_pi/firmware/u-boot-spl.wrapped.bin 		--dt /build/peach_pi/firmware/dtb/exynos5422-peach-pi.dtb 		--uboot /build/peach_pi/firmware/u-boot.bin 		 		--bootcmd vboot_twostop 		--bootsecure 		--add-config-int load-environment 0 		 --add-config-int silent_console 1
chromeos-bootimage-0.0.2-r1091:  * 

jecht:

chromeos-bootimage-0.0.2-r1091: Creating GBB...
chromeos-bootimage-0.0.2-r1091:                
chromeos-bootimage-0.0.2-r1091: Command failed: /usr/bin/cbfstool out.ro/coreboot-full.rom add -f /build/jecht/firmware/rocbfs/locale_da.bin -n locale_da.bin -t raw -c lzma
chromeos-bootimage-0.0.2-r1091: Performing operation on 'COREBOOT' region...
chromeos-bootimage-0.0.2-r1091: E: Could not add [/build/jecht/firmware/rocbfs/locale_da.bin, 13117 bytes (12 KB)@0x0]; too big?
chromeos-bootimage-0.0.2-r1091: E: Failed to add '/build/jecht/firmware/rocbfs/locale_da.bin' into ROM image.
chromeos-bootimage-0.0.2-r1091: E: Failed while operating on 'COREBOOT' region!
chromeos-bootimage-0.0.2-r1091: E: The image will be left unmodified.


 
Could these be caused by some kind of network failure?

Comment 2 by dlaurie@google.com, Jul 15 2016

I think it may be fallout from https://bugs.chromium.org/p/chromium/issues/detail?id=622501
Cc: wuchengli@chromium.org
Owner: dnojiri@chromium.org
Status: Assigned (was: Untriaged)
This is still failing in tot. From peach_pi-release builder, 598 passed and 599 failed. 598 is 8576.0.0 and 599 is 8577.0.0. The patch in http://crbug.com/622501 is also in the range. Daisuke. Please take a look.

https://crosland.corp.google.com/log/8576.0.0..8577.0.0

https://uberchromegw.corp.google.com/i/chromeos/builders/peach_pi-release?numbuilds=50
jecht release builder failed with the same error.
https://uberchromegw.corp.google.com/i/chromeos/builders/jecht-release?numbuilds=25
Status: Started (was: Assigned)
Project Member

Comment 6 by bugdroid1@chromium.org, Jul 18 2016

Labels: merge-merged-chromeos-2016.05
The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/coreboot/+/c859ce04d2df5f21c47a164cabbc9ef6dec61818

commit c859ce04d2df5f21c47a164cabbc9ef6dec61818
Author: Daisuke Nojiri <dnojiri@chromium.org>
Date: Mon Jul 18 17:48:25 2016

jecht: Increase RO coreboot size on flash

Bitmap images has been moved to CBFS from GBB. This patch adjusts the flash
size accordingly for jecht.

BUG=chromium:622501, chromium:628494 
BRANCH=none
TEST=emerge-jecht chromeos-bootimage
CQ-DEPEND=CL:361380

Change-Id: I50a9ade2e90237b0a7c277bffd7b540132415f13
Signed-off-by: Daisuke Nojiri <dnojiri@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/361370
Reviewed-by: Aaron Durbin <adurbin@chromium.org>

[modify] https://crrev.com/c859ce04d2df5f21c47a164cabbc9ef6dec61818/src/mainboard/google/jecht/chromeos.fmd

Project Member

Comment 7 by bugdroid1@chromium.org, Jul 18 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/platform/depthcharge/+/2e3bfaafca225582b33d892405395889d5390111

commit 2e3bfaafca225582b33d892405395889d5390111
Author: Daisuke Nojiri <dnojiri@chromium.org>
Date: Mon Jul 18 18:04:57 2016

jecht: Increase RO coreboot size on flash

Bitmap images has been moved to CBFS from GBB. This patch adjusts the flash
size accordingly for jecht.

BUG=chromium:622501, chromium:628494 
BRANCH=none
TEST=emerge-jecht chromeos-bootimage
CQ-DEPEND=CL:361370

Change-Id: I1ef5c2487652a548cae2acb6a94efc553d1e09bf
Signed-off-by: Daisuke Nojiri <dnojiri@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/361380
Reviewed-by: Aaron Durbin <adurbin@chromium.org>

[modify] https://crrev.com/2e3bfaafca225582b33d892405395889d5390111/board/jecht/fmap.dts

Project Member

Comment 8 by bugdroid1@chromium.org, Jul 18 2016

Status: Fixed (was: Started)
Please verify and reopen it if it's not fixed.
Labels: VerifyIn-54
Status: Verified (was: Fixed)
bulk verified

Sign in to add a comment