As seen in Autobuilder: https://autobuilder.yocto.io/builders/nightly-oe-selftest/builds/458/steps/Running%20oe-selftest/logs/stdio Relevant part: 2017-08-18 16:32:03,936 - oe-selftest - INFO - FAIL: test_stoptask_behavior (buildoptions.DiskMonTest) 2017-08-18 16:32:03,936 - oe-selftest - INFO - ---------------------------------------------------------------------- 2017-08-18 16:32:03,936 - oe-selftest - INFO - Traceback (most recent call last): File "/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-oe-selftest/build/meta/lib/oeqa/core/decorator/__init__.py", line 32, in wrapped_f return func(*args, **kwargs) File "/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-oe-selftest/build/meta/lib/oeqa/selftest/cases/buildoptions.py", line 69, in test_stoptask_behavior self.assertTrue('WARNING: The free space' in res.output, msg = "A warning should have been displayed for disk monitor is set to WARN: %s" %res.output) AssertionError: False is not true : A warning should have been displayed for disk monitor is set to WARN: NOTE: Starting bitbake server... Parsing recipes...done.
I believe this failure was caused by a large change in disk usage from another build process on the worker whilst this test was running. In general this doesn't happen and it was a case of unfortunate timing. The infrstrusture setup with multiple workers running in parallel on machines means this kind of thing would be very hard to fix without for example separate partitions for the different workers. Closing as WONTFIX as a one off issue. Will reconsider if we started seeing this regularly.