Bug 13150 - Test report contains UNKNOWN status when tests were skipped
Summary: Test report contains UNKNOWN status when tests were skipped
Status: CLOSED FIXED
Alias: None
Product: Runtime Testing
Classification: QA/Testing
Component: general (show other bugs)
Version: 2.8
Hardware: x86 Multiple
: Medium+ normal
Target Milestone: 2.6.3
Assignee: Armin Kuster
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2019-01-24 15:53 UTC by Ross Burton
Modified: 2019-07-11 15:21 UTC (History)
1 user (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ross Burton 2019-01-24 15:53:00 UTC 
The python.PythonTest class skips the entire class if python3 isn't present.  However this results in bad output in the JSON test results:

            "python.PythonTest.test_python3": {
                "status": "UNKNOWN"
            }

If a class skips, every test there should be marked a SKIPPED (with the message).
Comment 1 Richard Purdie 2019-05-09 13:48:05 UTC 
I tested this and its fine with master. Not sure if its an issue only with say thud or sumo?
Comment 2 Armin Kuster 2019-06-20 15:05:15 UTC 
do see this in warrior anymore.
https://autobuilder.yocto.io/pub/non-release/20190615-11/testresults/qemux86-64-ptest/python3.log
Comment 3 Armin Kuster 2019-07-11 15:20:01 UTC 
I dont see this in warrior
Comment 4 Armin Kuster 2019-07-11 15:21:16 UTC 
not in thud either.
Comment 5 Armin Kuster 2019-07-11 15:21:25 UTC 
closing