13605 2019-10-20 15:53:40 +0000 [master-next] LockedSignatures.test_locked_signatures fails 2020-03-24 22:05:23 +0000 1 1 7 Build System, Metadata & Runtime OE-Core core 3.0 x86 Multiple RESOLVED FIXED https://errors.yoctoproject.org/Errors/Build/91473/ Medium+ normal 3.1 M3 1 akuster richard.purdie meta.mr.watcher meta.watcher randy.macleod --- --- Don't know oldest_to_newest 85405 0 akuster 2019-10-20 15:53:40 +0000 2019-10-19 10:10:56,740 - oe-selftest - INFO - ... FAIL 2019-10-19 10:10:56,741 - oe-selftest - INFO - 2: 35/35 188/366 (51.74s) (signing.LockedSignatures.test_locked_signatures) 2019-10-19 10:10:56,741 - oe-selftest - INFO - testtools.testresult.real._StringException: Traceback (most recent call last): File "/home/pokybuild/yocto-worker/oe-selftest-centos/build/meta/lib/oeqa/selftest/cases/signing.py", line 219, in test_locked_signatures self.assertIsNotNone(found_warn, "Didn't find the expected warning message. Output: %s" % ret.output) File "/usr/lib64/python3.6/unittest/case.py", line 1256, in assertIsNotNone self.fail(self._formatMessage(msg, standardMsg)) File "/usr/lib64/python3.6/unittest/case.py", line 687, in fail raise self.failureException(msg) AssertionError: unexpectedly None : Didn't find the expected warning message. Output: Loading cache...done. 85682 1 richard.purdie 2019-12-03 22:04:55 +0000 Happened again https://autobuilder.yoctoproject.org/typhoon/#/builders/80/builds/526 85696 2 richard.purdie 2019-12-04 13:04:22 +0000 Also seen in https://autobuilder.yoctoproject.org/typhoon/#/builders/56/builds/844 86676 3 richard.purdie 2020-03-06 08:51:53 +0000 I've tried for months to try and debug this. I've been unable to replicate locally. What was really revealing was adding in debug code into siggen where the warnings are stored in a string. Those warnings are later printed by code in sstate.bbclass calling the checkhashes() method. What was happening is that checkhashes() never appeared to run, hence the expected warnings were never shown, hence the test fails. The underlying locked sigs code appeared to be working correctly and it was a message logging issue. Later log messages are shown so its unlikely to be a client disconnection issue. The most likely way I believe that possible is that the checkhashes function was only called with one hash to check and there is an early return in there that could trigger. I was unable to figure out how to replicate such a scenario but its possible. We now have the summary parameter, so I've sent a patch to drop this other older piece of code. 86804 4 richard.purdie 2020-03-24 22:05:23 +0000 http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=67511eda71affb6a0c9bfab37f59a53d35ac30c0