| Summary: | oe-selftest oelib.utils.TestMultiprocessLaunch.test_multiprocesslaunch failure | ||
|---|---|---|---|
| Product: | [QA/Testing] Functional (self) Testing | Reporter: | Richard Purdie <richard.purdie> |
| Component: | oe-selftest | Assignee: | Richard Purdie <richard.purdie> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | alexandre.belloni, Jagadheesan_Duraisamy, mhalstead, oobitots, randy.macleod, tvgamblin |
| Version: | 2.7 | ||
| Target Milestone: | 3.4 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | AB-INT | ||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Richard Purdie
2018-12-01 12:35:49 UTC
Note that I have merged some fixes to this test already but this looks like a separate issue. It's good to get self-tests working reliably sooner rather than later so target milestone should be 3.1-M1 but Qi already has 2 self-tests for M1 so this one can be 3.1-M2. Sakib. Please run this test in a loop on a 100s of core machine. Interestingly, I never seem to actually get to this failure point when running "oe-selftest -r oelib.utils.TestMultiprocessLaunch.test_multiprocesslaunch", but rather the test sequence seems to get stuck around test_checkpkg. Not sure yet if this is because I'm triggering it wrong or something else. Also in https://autobuilder.yoctoproject.org/typhoon/#/builders/87/builds/1853/steps/14/logs/stdio, along with 4 other failures. |