From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: McClintock Matthew-B29882 <B29882@freescale.com>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 02/16] bitbake pseudo wrapper: Don't base success on bitbake return code
Date: Thu, 29 Sep 2011 19:27:01 +0100 [thread overview]
Message-ID: <1317320829.12332.107.camel@ted> (raw)
In-Reply-To: <CAEsOVNdPjWvgaCL0EYUqh1XOriYMstGz3iLMG3Mamwd4sW9QQA@mail.gmail.com>
On Thu, 2011-09-29 at 18:04 +0000, McClintock Matthew-B29882 wrote:
> On Thu, Sep 29, 2011 at 3:26 AM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > On Wed, 2011-09-28 at 23:20 -0500, Matthew McClintock wrote:
> >> bitbake does not return 0 when a build succeeds.
> >
> > Er, yes it does. If you're seeing something other than 0 its likely
> > because you're seeing ERROR messages?
>
> First off, this appears to have been fixed along the way. But I know I
> was getting a message like:
>
> [snip]
> NOTE: Tasks Summary: Attempted 133 tasks of which 0 didn't need to be
> rerun and 0 failed.
Can you file an enhancement bug to list the number of errors and
warnings shown in the summary please? :)
We need to make it more obvious how many warnings/errors are occurring
since errors change the exit code.
> Then it would stop after building pseudo-native. Maybe we should add a
> message to scripts/bitbake so we get an actual failure message when
> this occurs? Also, are these errors relevant if we built psuedo-native
> properly?
Hard to say without seeing what they were...
Cheers,
Richard
next prev parent reply other threads:[~2011-09-29 18:32 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-29 4:20 [PATCH 01/16] libnl2: Fix a race on route/pktloc_syntax.h Matthew McClintock
2011-09-29 4:20 ` [PATCH 02/16] bitbake pseudo wrapper: Don't base success on bitbake return code Matthew McClintock
2011-09-29 8:26 ` Richard Purdie
2011-09-29 18:04 ` McClintock Matthew-B29882
2011-09-29 18:27 ` Richard Purdie [this message]
2011-09-29 18:30 ` McClintock Matthew-B29882
2011-09-29 4:20 ` [PATCH 03/16] Update gitignore to ignore all meta-* directories Matthew McClintock
2011-09-29 6:45 ` Dmitry Eremin-Solenikov
2011-09-29 4:20 ` [PATCH 04/16] Add support for generating ext2.bz2{, .u-boot} images Matthew McClintock
2011-09-29 4:20 ` [PATCH 05/16] Add support for generating ext2.lzma{, " Matthew McClintock
2011-09-29 4:21 ` [PATCH 06/16] Fix perl for powerpc64 build Matthew McClintock
2011-09-29 4:21 ` [PATCH 07/16] Fix lttng-ust for powerpc64 Matthew McClintock
2011-09-29 15:50 ` Richard Purdie
2011-09-29 18:21 ` McClintock Matthew-B29882
2011-09-29 18:46 ` Richard Purdie
2011-09-30 16:58 ` Saul Wold
2011-09-30 17:19 ` McClintock Matthew-B29882
2011-09-29 4:21 ` [PATCH 08/16] Fixup kexec-tools compatible host for powerpc Matthew McClintock
2011-09-29 4:21 ` [PATCH 09/16] Add autoconf cache for screen on powerpc64 Matthew McClintock
2011-09-29 4:21 ` [PATCH 10/16] Fix mdadm for powerpc64 Matthew McClintock
2011-09-29 15:51 ` Richard Purdie
2011-09-29 18:19 ` McClintock Matthew-B29882
2011-09-29 4:21 ` [PATCH 11/16] Fix ghostscript on powerpc64 Matthew McClintock
2011-09-29 4:21 ` [PATCH 12/16] Fix flac build on e500mc cores Matthew McClintock
2011-09-29 15:52 ` Richard Purdie
2011-09-29 18:10 ` McClintock Matthew-B29882
2011-09-29 18:31 ` Richard Purdie
2011-09-29 4:21 ` [PATCH 13/16] Fix HAL on newer kernels without header file Matthew McClintock
2011-09-29 4:21 ` [PATCH 14/16] Add udev patch to compile against newer kernels Matthew McClintock
2011-09-29 4:21 ` [PATCH 15/16] Fix sysklogd build on e500v2 cores Matthew McClintock
2011-09-29 4:21 ` [PATCH 16/16] Add proper deps for nfs-utils, util-linux, and strace Matthew McClintock
2011-09-29 15:55 ` Richard Purdie
2011-09-29 15:47 ` [PATCH 01/16] libnl2: Fix a race on route/pktloc_syntax.h Richard Purdie
2011-09-29 18:28 ` McClintock Matthew-B29882
2011-09-29 18:38 ` Richard Purdie
2011-09-30 17:01 ` Saul Wold
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=1317320829.12332.107.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=B29882@freescale.com \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox