chromeos-bootimage build failed on veyron_romy |
||||
Issue descriptionIt started from build #941 and is failing consistently. https://chromegw.corp.google.com/i/chromeos/builders/veyron-d-release-group/builds/941 The blamelist: https://crosland.corp.google.com/log/8164.0.0..8165.0.0 Error messages: chromeos-bootimage-0.0.2-r968: Command failed: /usr/bin/cbfstool out.dev/coreboot-full.rom add-payload -f /build/veyron_romy/firmware/depthcharge/dev.elf -n fallback/payload -c lzma chromeos-bootimage-0.0.2-r968: Performing operation on 'COREBOOT' region... chromeos-bootimage-0.0.2-r968: E: Could not add [/build/veyron_romy/firmware/depthcharge/dev.elf, 82479 bytes (80 KB)@0x0]; too big? chromeos-bootimage-0.0.2-r968: E: Failed to add '/build/veyron_romy/firmware/depthcharge/dev.elf' into ROM image. chromeos-bootimage-0.0.2-r968: E: Failed while operating on 'COREBOOT' region! chromeos-bootimage-0.0.2-r968: E: The image will be left unmodified. It complained about file size too big. I am guessing if this is related to https://bugs.chromium.org/p/chromium/issues/detail?id=501060 where CL https://chromium-review.googlesource.com/#/c/337205/ did add 255KB into firmware.
,
Apr 11 2016
,
Apr 12 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/23071b9112dbc9c84096c4ae26f3b55915779804 commit 23071b9112dbc9c84096c4ae26f3b55915779804 Author: Daisuke Nojiri <dnojiri@chromium.org> Date: Mon Apr 11 20:07:31 2016 veyron_romy: Increase RO CBFS size by 512 Kb This change increases the size of RO CBFS by 512 Kb to accommodate new images added to the INSERT screen. BUG= chromium:602147 BRANCH=tot TEST=emerge-veyron_romy chromeos-bootimage CQ-DEPEND=CL:338095,CL:338152 Change-Id: I675676dd590aa91ce424b04c78675564d422fea9 Signed-off-by: Daisuke Nojiri <dnojiri@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/338027 [modify] https://crrev.com/23071b9112dbc9c84096c4ae26f3b55915779804/sys-boot/coreboot/files/configs/config.veyron_romy [rename] https://crrev.com/23071b9112dbc9c84096c4ae26f3b55915779804/sys-boot/coreboot/coreboot-0.0.1-r1482.ebuild
,
Apr 12 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/third_party/coreboot/+/4692cad8fc939202af2e3de709c2835a854e64b2 commit 4692cad8fc939202af2e3de709c2835a854e64b2 Author: Daisuke Nojiri <dnojiri@chromium.org> Date: Mon Apr 11 20:02:59 2016 veyron_romy: Increase RO CBFS size by 512 Kb This change increases the size of RO CBFS by 512 Kb to accommodate new images added to the INSERT screen. BUG= chromium:602147 BRANCH=tot TEST=emerge-veyron_romy chromeos-bootimage CQ-DEPEND=CL:338152,CL:338027 Change-Id: I2f117247b2971a6f5576f60cdd53624ad6867e78 Signed-off-by: Daisuke Nojiri <dnojiri@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/338095 Reviewed-by: David Hendricks <dhendrix@chromium.org> Reviewed-by: Julius Werner <jwerner@chromium.org> [modify] https://crrev.com/4692cad8fc939202af2e3de709c2835a854e64b2/src/mainboard/google/veyron_romy/chromeos.fmd
,
Apr 12 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/platform/depthcharge/+/d7f06f6b5f44ca381233ce501a17016e228aa3d9 commit d7f06f6b5f44ca381233ce501a17016e228aa3d9 Author: Daisuke Nojiri <dnojiri@chromium.org> Date: Mon Apr 11 20:13:39 2016 veyron_romy: Increase RO CBFS size by 512 Kb This change increases the size of RO CBFS by 512 Kb to accommodate new images added to the INSERT screen. BUG= chromium:602147 BRANCH=tot TEST=emerge-veyron_romy chromeos-bootimage CQ-DEPEND=CL:338027,CL:338095 Change-Id: Ib51f475bd271c796e6dce91a449411070d2cdf11 Signed-off-by: Daisuke Nojiri <dnojiri@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/338152 Reviewed-by: Julius Werner <jwerner@chromium.org> [modify] https://crrev.com/d7f06f6b5f44ca381233ce501a17016e228aa3d9/board/veyron_romy/fmap.dts
,
Apr 13 2016
BuildPackages stage green for romy on build 955 : https://chromegw.corp.google.com/i/chromeos/builders/veyron-d-release-group/builds/955 |
||||
►
Sign in to add a comment |
||||
Comment 1 by cychiang@chromium.org
, Apr 11 2016