]> code.ossystems Code Review - openembedded-core.git/commit
oeqa/oetest.py: use bb logging
authorPatrick Ohly <patrick.ohly@intel.com>
Thu, 9 Apr 2015 09:24:22 +0000 (02:24 -0700)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Thu, 9 Apr 2015 18:48:01 +0000 (19:48 +0100)
commit4b6f87a82ece230b7296f1577d4092ef559af1d4
tree40a1e8e1a58133e4aa43773884862b250b2abbd0
parent4ac5d1011fe6b5bba9511416082891e925cbd03c
oeqa/oetest.py: use bb logging

Plain print has two drawbacks:
- the output is handled by different processes, causing the message
  about found tests to appear randomly after the result of the initial
  tests
- the output is not part of the bitbake console output

Affects image testing with testimage.bbclass.

Signed-off-by: Patrick Ohly <patrick.ohly@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
meta/lib/oeqa/oetest.py