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

Issue 775766 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: Nov 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

chromeos-config-tools unittest broke CQ

Project Member Reported by nxia@chromium.org, Oct 18 2017

Issue description

https://luci-milo.appspot.com/buildbot/chromeos/guado_moblab-paladin/7576


chromeos-config-tools-0.0.1-r665: Running tests in ./cros_config_host_py/libcros_config_host_unittest.py
chromeos-config-tools-0.0.1-r665: .........F.......
chromeos-config-tools-0.0.1-r665: ======================================================================
chromeos-config-tools-0.0.1-r665: FAIL: testGetTouchFirmwareFiles (__main__.CrosConfigHostTest)
chromeos-config-tools-0.0.1-r665: ----------------------------------------------------------------------
chromeos-config-tools-0.0.1-r665: Traceback (most recent call last):
chromeos-config-tools-0.0.1-r665:   File "././cros_config_host_py/libcros_config_host_unittest.py", line 134, in testGetTouchFirmwareFiles
chromeos-config-tools-0.0.1-r665:     TouchFile(firmware='wacom/4209.hex', symlink='wacom_firmware_PYRO.bin')
chromeos-config-tools-0.0.1-r665: AssertionError: Lists differ: [TouchFile(firmware='elan/0a97... != [TouchFile(firmware='elan/0a97...
chromeos-config-tools-0.0.1-r665: 
chromeos-config-tools-0.0.1-r665: First differing element 5:
chromeos-config-tools-0.0.1-r665: TouchFile(firmware='wacom/4209.hex', symlink='wacom_firmware_WHITETIP2.bin')
chromeos-config-tools-0.0.1-r665: TouchFile(firmware='wacom/4209.hex', symlink='wacom_firmware_PYRO.bin')
chromeos-config-tools-0.0.1-r665: 
chromeos-config-tools-0.0.1-r665: First list contains 3 additional elements.
chromeos-config-tools-0.0.1-r665: First extra element 6:
chromeos-config-tools-0.0.1-r665: TouchFile(firmware='wacom/4209.hex', symlink='wacom_firmware_WHITETIP.bin')
chromeos-config-tools-0.0.1-r665: 
chromeos-config-tools-0.0.1-r665: Diff is 925 characters long. Set self.maxDiff to None to see it.
chromeos-config-tools-0.0.1-r665: 
chromeos-config-tools-0.0.1-r665: ----------------------------------------------------------------------
chromeos-config-tools-0.0.1-r665: Ran 17 tests in 0.256s
chromeos-config-tools-0.0.1-r665: 
chromeos-config-tools-0.0.1-r665: FAILED (failures=1)
chromeos-config-tools-0.0.1-r665:  * ERROR: chromeos-base/chromeos-config-tools-0.0.1-r665::chromiumos failed (test phase):
chromeos-config-tools-0.0.1-r665:  *   cros_config unit tests have errors
 

Comment 1 by nxia@chromium.org, Oct 18 2017

Summary: chromeos-config-tools unittest broke CQ (was: chromeos-config-tools broke CQ)

Comment 3 by sjg@chromium.org, Oct 18 2017

I think this was due to a test relying on the order of two namedtuple objects, where the first field was the same for two of them, and thus the order was indeterminate.

I resubmitted the CLs without that.

I don't think this is a problem with test coverage, and in particular it doesn't matter which board you run chromeos-config-tools on. It is board-agnostic.

Comment 4 by sjg@chromium.org, Oct 18 2017

Labels: -Pri-0 Pri-3
We should consider reverting

https://chromium-review.googlesource.com/c/chromiumos/platform/firmware/+/724364

and just run the pre-CQ on one board, or perhaps one ARM, one x86.

Comment 5 by sjg@chromium.org, Nov 4 2017

Labels: Unibuild

Comment 6 by sjg@chromium.org, Nov 10 2017

Owner: la...@chromium.org
You may have fixed this - assigning to you

Comment 7 by la...@chromium.org, Nov 10 2017

Status: Fixed (was: Untriaged)
I didn't fix it, but I also haven't seen this error. Lets call it fixed.

Sign in to add a comment