]> code.ossystems Code Review - openembedded-core.git/commit
oeqa/core/runner: OEStreamLogger don't buffer test execution writes
authorAníbal Limón <anibal.limon@linux.intel.com>
Wed, 26 Jul 2017 15:04:10 +0000 (10:04 -0500)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Sun, 30 Jul 2017 07:45:11 +0000 (08:45 +0100)
commit4c2276469f58a88f864eb374c00dbbaace702de4
treed4e66b76c3702b999cdf0377b9d36194ad384bcc
parente50b415aaaa1581473f85f0a8afa278b5f95129b
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]

Signed-off-by: Aníbal Limón <anibal.limon@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
meta/lib/oeqa/core/runner.py