Aníbal Limón 0f0368d052 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>

2017-07-30 08:46:19 +01:00

..

oe

oe/copy_buildsystem: check_sstate_task_list also pop BBPATH from env

2017-07-21 08:44:25 +01:00

oeqa

oeqa/core/runner: OEStreamLogger don't buffer test execution writes

2017-07-30 08:46:19 +01:00

buildstats.py

meta: remove True option to getVar calls

2016-12-16 10:23:23 +00:00

rootfspostcommands.py

rootfspostcommands: remove shadow backup files instead of trying to sort

2017-02-19 06:16:58 -08:00