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

Issue 709110 link

Starred by 1 user

Issue metadata

Status: Archived
Owner:
Closed: Apr 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 0
Type: Bug-Regression



Sign in to add a comment

gale/whirlwind firmware "test" builds fail with "No module named libfdt"

Project Member Reported by grundler@google.com, Apr 6 2017

Issue description


./build_packages --board=$B --withautotest

fails with:
chromeos-firmware-gale-0.0.1-r51: Traceback (most recent call last):
chromeos-firmware-gale-0.0.1-r51:   File "./pack_firmware.py", line 33, in <module>
chromeos-firmware-gale-0.0.1-r51:     import libfdt
chromeos-firmware-gale-0.0.1-r51: ImportError: No module named libfdt
chromeos-firmware-gale-0.0.1-r51:  * ERROR: chromeos-base/chromeos-firmware-gale-0.0.1-r51::gale-private failed (compile phase):
chromeos-firmware-gale-0.0.1-r51:  *   Cannot pack firmware using Python script.

This is the change that caused the failure:
https://chromium-review.googlesource.com/455229

However, "emerge-gale chromeos-firmware-gale" does succeed. (ie drop "FEATURES=test")

So in this case, the arkham/whirlwind/gale test builds appear to be missing a dependency on dtc package.
 

Comment 1 by sjg@chromium.org, Apr 6 2017

Status: Started (was: Assigned)
Project Member

Comment 2 by bugdroid1@chromium.org, Apr 7 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/93dbf87a4df8b126c0cd11ce3eefa2def2c0cbbf

commit 93dbf87a4df8b126c0cd11ce3eefa2def2c0cbbf
Author: Simon Glass <sjg@chromium.org>
Date: Fri Apr 07 21:15:38 2017

target-chromium-os-sdk: Make sure that dtc is available

This is needed to run firmware packaging tests (chromeos-firmware-<board>)
so install it as part of the sdk.

BUG= chromium:709110 
TEST=sudo emerge --unmerge dtc; ./build_packages --board=reef --nowithautotest
See that it installs dtc as part of 'Updating the SDK'

Change-Id: Iac6bfcac6ab0d387c04cfb2128fe0ba59a972e1d
Signed-off-by: Simon Glass <sjg@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/470267
Commit-Ready: Grant Grundler <grundler@chromium.org>
Reviewed-by: Grant Grundler <grundler@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>

[modify] https://crrev.com/93dbf87a4df8b126c0cd11ce3eefa2def2c0cbbf/virtual/target-chromium-os-sdk/target-chromium-os-sdk-1.ebuild
[rename] https://crrev.com/93dbf87a4df8b126c0cd11ce3eefa2def2c0cbbf/virtual/target-chromium-os-sdk/target-chromium-os-sdk-1-r72.ebuild

Comment 3 by sjg@chromium.org, Apr 7 2017

Cc: grundler@chromium.org
Status: Fixed (was: Started)

Comment 4 by sjg@chromium.org, Apr 7 2017

Summary: gale/whirlwind firmware "test" builds fail with "No module named libfdt" (was: gale/whirlwind firmeware "test" builds fail with "No module named libfdt")

Comment 5 by dchan@google.com, May 30 2017

Labels: VerifyIn-60

Comment 6 by dchan@chromium.org, Aug 1 2017

Labels: VerifyIn-61

Comment 7 by dchan@chromium.org, Jan 22 2018

Status: Archived (was: Fixed)

Sign in to add a comment