]> code.ossystems Code Review - openembedded-core.git/commit
oeqa: Clean up logger handling
authorRichard Purdie <richard.purdie@linuxfoundation.org>
Wed, 8 Nov 2017 18:17:17 +0000 (18:17 +0000)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Sat, 3 Mar 2018 08:32:14 +0000 (08:32 +0000)
commit22003f97ff7f53c32999dc466d26c1471ead9b6b
tree89c497a9e82846f869b22410995c6a65490ff063
parent31b8991de32ce91af58eab183f283adcded737c2
oeqa: Clean up logger handling

The logger handling in oeqa was confused at best. This patch:

a) Passes in a logger through various qemu runner pieces
b) Uses that logger consistently in the code
c) Creates a logger for QemuRunner outside the bitbake namespace
   meaning we don't conflict with the tinfoil logging changes

The result of this is more consistency. For runtime tests in testimage,
the logs always contain the debug info, nothing is shwon on the console.
For the oe-selftests, logs are intercepted and only shown if the test
fails.

(From OE-Core rev: ba8babc45141891d0624f9a181a580fa416e87ec)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Armin Kuster <akuster@mvista.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Armin Kuster <akuster808@gmail.com>
meta/lib/oeqa/core/target/qemu.py
meta/lib/oeqa/selftest/runqemu.py
meta/lib/oeqa/targetcontrol.py
meta/lib/oeqa/utils/commands.py
meta/lib/oeqa/utils/qemurunner.py
meta/lib/oeqa/utils/qemutinyrunner.py