Bug 10050

Summary: oeqa runner generate wrong test results in log file when running dynamic test cases
Product: [QA/Testing] Runtime Testing Reporter: dawei <daweix.wu>
Component: generalAssignee: Unassigned <unassigned>
Status: RESOLVED OBSOLETE QA Contact:
Severity: enhancement    
Priority: Medium CC: jose.perez.carranza, joshuagloe, patrick.ohly, randy.macleod, sgw
Version: 2.4   
Target Milestone: Future   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Don't know
Attachments:
Description Flags
Test case none

Description dawei 2016-07-29 07:01:59 UTC
Created attachment 3333 [details]
Test case

Details:
The results is correct printed on screen but not correct in log file

Step:

Use yocto oeqa runner to run the attach test cases

*Expected Results:*
See pass/fail/skip/error 4 results in log file

*Actual Results:*
All passed in log file
Comment 1 dawei 2016-07-29 07:08:26 UTC
From Zhang,Junhui:
there is a workaround in line 19 , if comment it out , this issue is not reproduced. You can see more explanation there.
Comment 2 Benjamin Esquivel 2016-07-29 15:00:00 UTC
Mariano, can you replicate this test?
Comment 3 Mariano Lopez 2016-07-29 21:17:04 UTC
In the test cases attached it creates dynamically the class and the for every new class it creates a TextTestResult, so this can lead to the behaviour observed.

OE doesn't use/require dynamic generated test.
Comment 4 dawei 2016-08-02 08:07:20 UTC
For us , we need this function to generate logs for this case:

One oe runner static *Total* case includes many real cases , so to the runner, it just only generate one result for those many real cases in the log file, which doesn't reflect the real results.
Comment 5 Jair Gonzalez 2017-08-29 21:53:19 UTC
Moving to 2.5, due to limited resources.
Comment 6 Jair Gonzalez 2017-08-29 22:03:10 UTC
Returning version to 2.4.
Comment 7 Joshua Lock 2017-12-07 15:12:54 UTC
Much of the oeqa code has been rewritten since this issue was filed, need to test whether the issue is still present.
Comment 8 Randy MacLeod 2020-04-09 15:28:27 UTC
If this problem shows up again, reopen.