Bug 8576 - QemuRunner logging for qemu start failure does not log anything to the console in oe-selftest
Summary: QemuRunner logging for qemu start failure does not log anything to the consol...
Status: RESOLVED FIXED
Alias: None
Product: Runtime Testing
Classification: QA/Testing
Component: general (show other bugs)
Version: 1.7
Hardware: x86 Multiple
: Medium+ major
Target Milestone: 2.2 M4
Assignee: Francisco Pedraza
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2015-10-26 14:11 UTC by Paul Eggleton
Modified: 2017-12-06 16:49 UTC (History)
1 user (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Eggleton 2015-10-26 14:11:08 UTC 
From https://autobuilder.yoctoproject.org/main/builders/nightly-oe-selftest/builds/234/steps/Running%20oe-selftest/logs/stdio we can see that when an oe-selftest test uses QemuRunner, if qemu fails to start we just get a "SystemExit" plus the backtrace to it - we do not see the calls to logger.info(), so without making an ssh connection into the machine we've got no idea what the failure is.
Comment 1 Alexandru Georgescu 2016-01-12 11:36:26 UTC 
Costin, can you help on this one?
Comment 2 Francisco Pedraza 2016-09-27 17:09:54 UTC 
I am going to work on this.
Comment 3 Francisco Pedraza 2016-09-28 22:20:43 UTC 
I have sent a patch to contrib, waiting for review -> http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=QemuRunner&id=115ac38a8711d866480b0a0ecd6a530e64bfc017
Comment 4 Francisco Pedraza 2016-10-04 16:01:18 UTC 
The patch is in master: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=7ae326c76bd7c357d11974db618eb65956b57d44
Regards,
Paco