New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Starred by 1 user
Status: WontFix
Owner:
Closed: Feb 9
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment
coral-paladin failed on pack_firmware_unittest.py
Project Member Reported by shenghao@chromium.org, Feb 9 Back to list
pack_firmware_unittest.py failed on several boards (coral, fizz, etc) in CQ:

chromeos-firmware-coral-0.0.1-r84: Traceback (most recent call last):
chromeos-firmware-coral-0.0.1-r84:   File "pack_firmware_unittest.py", line 33, in <module>
chromeos-firmware-coral-0.0.1-r84:     from libcros_config_host import libcros_config_host
chromeos-firmware-coral-0.0.1-r84: ImportError: No module named libcros_config_host
chromeos-firmware-coral-0.0.1-r84:  * ERROR: chromeos-base/chromeos-firmware-coral-0.0.1-r84::coral-private failed (test phase):
chromeos-firmware-coral-0.0.1-r84:  *   Tests failed at pack_firmware_unittest.py
chromeos-firmware-coral-0.0.1-r84:  * 
chromeos-firmware-coral-0.0.1-r84:  * Call stack:
chromeos-firmware-coral-0.0.1-r84:  *     ebuild.sh, line  133:  Called src_test
chromeos-firmware-coral-0.0.1-r84:  *   environment, line 3805:  Called cros-firmware_src_test
chromeos-firmware-coral-0.0.1-r84:  *   environment, line 1014:  Called die
chromeos-firmware-coral-0.0.1-r84:  * The specific snippet of code:
chromeos-firmware-coral-0.0.1-r84:  *           python "${fname}" || die "Tests failed at ${fname}";

https://uberchromegw.corp.google.com/i/chromeos/builders/coral-paladin/builds/2494

Assigning to the owner of pack_firmware_unittest.py.
sjg@, could you route to relevant person?

 
Status: WontFix
It's passing now.
Sign in to add a comment