Bug 4398

Summary: "all succeeded" does not look like a reason to fail a build
Product: [Build System, Metadata & Runtime] BitBake Reporter: Robert Yang <liezhi.yang>
Component: bitbakeAssignee: Robert Yang <liezhi.yang>
Status: RESOLVED DUPLICATE QA Contact:
Severity: normal    
Priority: Undecided CC: poky.bs.watcher, poky.watcher, richard.purdie, sgw
Version: 1.5   
Target Milestone: 1.5 M1   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: ---

Description Robert Yang 2013-04-23 09:27:28 UTC 
Marcin Juszkiewicz wrote:
> 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.

RP's reply:

Agreed, please open a bug for it.

FWIW Bitbake will set a non-zero exit code if any error messages appear,
as the message says. Whilst people find that confusing, I continue to
believe it is the right thing to be doing and we need to tighten up
things in other places as I describe above. That error code does help us
catch problems on the autobuilders and so forth.
Comment 1 Robert Yang 2013-04-23 09:30:40 UTC 
Duplicate to 4397

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