Bug 4398 - "all succeeded" does not look like a reason to fail a build
Summary: "all succeeded" does not look like a reason to fail a build
Status: RESOLVED DUPLICATE of bug 4397
Alias: None
Product: BitBake
Classification: Build System, Metadata & Runtime
Component: bitbake (show other bugs)
Version: 1.5
Hardware: x86 Multiple
: Undecided normal
Target Milestone: 1.5 M1
Assignee: Robert Yang
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2013-04-23 09:27 UTC by Robert Yang
Modified: 2013-04-23 09:30 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---

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 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 ***