From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: bitbake exit codes? (testing-release-2011.03 build results)
Date: Mon, 14 Feb 2011 08:01:17 -0700 [thread overview]
Message-ID: <4D5943BD.9040701@mentor.com> (raw)
In-Reply-To: <4D59066F.1040805@dresearch.de>
On 02/14/2011 03:39 AM, Steffen Sledz wrote:
> Am 14.02.2011 09:11, schrieb Frans Meulenbroeks:
>> 2011/2/14 Steffen Sledz<sledz@dresearch.de>:
>>> While setting up Jenkins/Hudson jobs for the testing-release-2011.03 branch based on the testscript.sh from the contrib subdir i hit the following problem.
>>>
>>> bitbake (1.10.2) finally reports "NOTE: Task Summary: Attempted 1217 tasks of which 0 didn't need to be rerun and 0 failed.". So it seems that the build was successful. But bitbake did not return 0 but 1. So Jenkins marks the build as failed.
>>>
>>> I guess the exit code 1 is coming from some QA Issues. How do we handle that if if my guess is right?
>>>
>>> Do we mark such a build run as successful in our test matrix?
>>>
>>> Has bitbake a defined set of exit codes that we can evaluate in the testscript.sh?
>>>
>>> Steffen
>>
>> There have been a few threads on this in the past.
>> One of the ways (and maybe the best one) to get around this is to fix
>> the QA errors.
>
> Of course. You are right.
>
> But for the moment the question is: "Do we mark such a builds as successful in our test matrix or not?"
Well, as the code stands today (post tag) the change to make those
failures kill the build have been merged.
--
Tom Rini
Mentor Graphics Corporation
prev parent reply other threads:[~2011-02-14 15:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-14 7:12 bitbake exit codes? Steffen Sledz
2011-02-14 8:11 ` Frans Meulenbroeks
2011-02-14 10:39 ` bitbake exit codes? (testing-release-2011.03 build results) Steffen Sledz
2011-02-14 13:25 ` Frans Meulenbroeks
2011-02-14 13:28 ` Frans Meulenbroeks
2011-02-14 15:01 ` Tom Rini [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D5943BD.9040701@mentor.com \
--to=tom_rini@mentor.com \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.