| Summary: |
selftest: using the xml test output plugin delays the test names in the execution log |
| Product: |
[QA/Testing] Build Testing
|
Reporter: |
Benjamin Esquivel <benjamin.esquivel> |
| Component: |
general | Assignee: |
Apoorv <apoorv.sangal> |
| Status: |
RESOLVED
WONTFIX
|
QA Contact: |
|
| Severity: |
minor
|
|
|
| Priority: |
Medium
|
CC: |
benjamin.esquivel, jose.perez.carranza, sangeeta.jain
|
| Version: |
unspecified | |
|
| Target Milestone: |
4.99 | |
|
| Hardware: |
x86 | |
|
| OS: |
Multiple | |
|
| Whiteboard: |
|
|
OS type for building Yocto:
|
---
|
Type of Regression:
|
---
|
|---|
|
Verified:
|
|
Documentation change:
|
No (bug/feature does not impact docs)
|
|---|
| Attachments: |
|
Created attachment 3634 [details] execution log Seems like the xml test output plugin (unittest-xml-reporting) is delaying the test names appearing at the execution log (stdout). When a test session is started, you see something like the execution log attachment in this bug. Then the first name of the test appears when the test is over. This is contrary to the logic and to the plain unittest output plugin (CustomTextTestRunner). To reproduce this behavior, just execute the all-tests filter: $ oe-selftest --run-all-tests It is worth mentioning that running the command as above it starts always with a test that takes a lot of time to finish. Meaning that with a shorter test (like using a different filter) you also get a faster test name appearing there. The suggestion is to investigate why/if the unittest-xml-reporting is purposely printing the test name when the test is over instead of when the test begins.