Bug 4397

Summary: BitBake does not break a build when ERROR is spotted
Product: [Build System, Metadata & Runtime] BitBake Reporter: Marcin Juszkiewicz <marcin>
Component: bitbakeAssignee: Richard Purdie <richard.purdie>
Status: RESOLVED DUPLICATE QA Contact:
Severity: normal    
Priority: Undecided CC: liezhi.yang, poky.bs.watcher, poky.watcher, sgw
Version: unspecified   
Target Milestone: ---   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: ---

Description Marcin Juszkiewicz 2013-04-23 09:24:30 UTC 
There is one thing which kind of bothers me. "ERROR" message which is just a warning. Like:

ERROR: libelf is listed in PACKAGES multiple times, this leads to packaging errors.
ERROR: libasm is listed in PACKAGES multiple times, this leads to packaging errors.
ERROR: libdw is listed in PACKAGES multiple times, this leads to packaging errors.
ERROR: libdw-dev is listed in PACKAGES multiple times, this leads to packaging errors.
ERROR: libasm-dev is listed in PACKAGES multiple times, this leads to packaging errors.
ERROR: libelf-dev is listed in PACKAGES multiple times, this leads to packaging errors.

If it is error then let BitBake exit instead of doing task. If it is not error but just a warning then let it be renamed?

My recent build failed with:

--------
NOTE: recipe linaro-image-minimal-1.0-r0: task do_rm_work_all: Started
NOTE: recipe linaro-image-minimal-1.0-r0: task do_rm_work_all: Succeeded
NOTE: Tasks Summary: Attempted 2247 tasks of which 915 didn't need to be rerun and all succeeded.

Summary: There were 3 WARNING messages shown.
Summary: There were 6 ERROR messages shown, returning a non-zero exit code.
Build step 'Execute shell' marked build as failure
--------

"all succeeded" does not look like a reason to fail a build.
Comment 1 Marcin Juszkiewicz 2013-04-23 09:26:42 UTC 
We are using EC2 for builds so each build costs money. And if I have to repeat 4h build (when sstate-cache is not enough) just to see build failure it bumps costs even more.

If BitBake thinks that error is error then let it errors out when it happens.
Comment 2 Robert Yang 2013-04-23 09:30:40 UTC 
*** Bug 4398 has been marked as a duplicate of this bug. ***
Comment 3 Saul Wold 2013-04-25 14:49:58 UTC 
See Dup, fix by using QA_WARN mechanism

*** This bug has been marked as a duplicate of bug 4396 ***