diff options
| author | Aníbal Limón <anibal.limon@linux.intel.com> | 2017-07-26 10:04:10 -0500 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2017-07-30 08:46:19 +0100 |
| commit | 0f0368d0527eacb13ac8547c2732219b0d4b64fe (patch) | |
| tree | caada67596d791de47d93c29a572959318807d88 /meta/recipes-rt | |
| parent | 2d50f153b5b76adbd4157d2f69001ed91e9148dc (diff) | |
| download | poky-0f0368d0527eacb13ac8547c2732219b0d4b64fe.tar.gz | |
oeqa/core/runner: OEStreamLogger don't buffer test execution writes
Since OEQA framework uses Python logging functionality to report test
results there is a class that wraps PyUnit writes into logging commands
(OEStreamLogger), so don't buffer the actual test execution to have
insight of what is currently executing.
This fix will change a little the test output format adding an '\n'
previous the test result, for example:
From:
test_nonmatching_checksum (lic_checksum.LicenseTests) ... ok
To:
test_nonmatching_checksum (lic_checksum.LicenseTests)
... ok
This is because the new line added by the PyUnit StreamLogger because
currently we don't have a manner to identify when a test execution
starts at report level (write msg).
[YOCTO #11827]
(From OE-Core rev: 4c2276469f58a88f864eb374c00dbbaace702de4)
Signed-off-by: Aníbal Limón <anibal.limon@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-rt')
0 files changed, 0 insertions, 0 deletions