Bug 11953

Summary: nightly-oe-selftest failed: FAIL: test_stoptask_behavior (buildoptions.DiskMonTest)
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Juro Bystricky <juro.bystricky>
Component: coreAssignee: Richard Purdie <richard.purdie>
Status: RESOLVED WONTFIX QA Contact:
Severity: normal    
Priority: Medium+ CC: meta.mr.watcher, meta.watcher
Version: 2.4   
Target Milestone: 2.4 M3   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)

Description Juro Bystricky 2017-08-18 17:01:08 UTC 
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.
Comment 1 Richard Purdie 2017-08-29 15:05:00 UTC 
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.