Bug 12920 - do_package QA error logs not show in console after failure
Summary: do_package QA error logs not show in console after failure
Status: RESOLVED WONTFIX
Alias: None
Product: Meta-yocto
Classification: Build System, Metadata & Runtime
Component: meta-yocto (show other bugs)
Version: 2.5.2
Hardware: x86 Multiple
: Medium+ minor
Target Milestone: 2.5.2
Assignee: mikko.rapeli
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2018-09-11 08:48 UTC by mikko.rapeli
Modified: 2020-07-23 07:47 UTC (History)
2 users (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 mikko.rapeli 2018-09-11 08:48:17 UTC 
In sumo, when "do_package: Fatal QA errors found, failing task" happens,
the build console log does not print the details.

Thus in CI builds it's very difficult to figure out what is causing the failure.

For details, developers need access to the build environment to access the log file. For example:

ERROR: Logfile of failure stored in: /home/builder/src/base/build/tmp/work/linux/bla/0.1-r1/temp/log.do_package.28432

and the log file will show that:

ERROR: QA Issue: File '/usr/bin/bla' from bla was already stripped, this will prevent future debugging! [already-stripped]

Would be nice to print the full QA task log to build output when the task fails. This happens with other QA checks.
Comment 1 Armin Kuster 2018-11-05 23:47:04 UTC 
how can I reproduce this ?
Comment 2 Armin Kuster 2018-11-13 16:36:38 UTC 
How can I reproduce this ?
Comment 3 mikko.rapeli 2018-12-17 08:16:36 UTC 
I'll send a patch next this happens.