If we run oe-selftest -r and there is a failure in setupClass, it doesn't get reported to the user clearly. A good example is this: http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=6f2ef620d90ab39870bb6c02183249e0e1045aeb which shows a clear error without the -j options but with it, it only shows: 2018-12-05 18:43:24,262 - oe-selftest - INFO - RESULTS - eSDK.oeSDKExtSelfTest.test_image_generation_binary_feeds - Testcase 1603: UNKNOWN 2018-12-05 18:43:24,262 - oe-selftest - INFO - RESULTS - eSDK.oeSDKExtSelfTest.test_install_libraries_headers - Testcase 1602: UNKNOWN (from https://autobuilder.yoctoproject.org/typhoon/#/builders/79/builds/55/steps/7/logs/step2d)
I should note the error is shown in the log but the summary at the end is wrong: All required tests passed (successes=334, skipped=2, failures=0, errors=0)
Another example: https://autobuilder.yoctoproject.org/typhoon/#/builders/84/builds/61
It's good to get selftests working reliably sooner rather than later so target milestone is 3.1-M1.
I tested and confirmed that Trevor's recent work did also fix this issue and its no longer present.