From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH] lib/bb/event: improve handling of event queue on exit
Date: Fri, 14 Sep 2012 09:28:37 +0100 [thread overview]
Message-ID: <1347611317.9456.3.camel@ted> (raw)
In-Reply-To: <1347356243-7920-1-git-send-email-paul.eggleton@linux.intel.com>
On Tue, 2012-09-11 at 10:37 +0100, Paul Eggleton wrote:
> If BitBake exits before a UI handler (server) has been registered, we
> print the event queue; if there are any errors or other non-debug
> messages just print these and suppress the rest of the message queue.
>
> This improves the output when sanity check failures occur with OE-Core
> by avoiding printing a long stream of uninformative debug messages.
>
> Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
> ---
> bitbake/lib/bb/event.py | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
Merged to master, thanks.
Richard
prev parent reply other threads:[~2012-09-14 8:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-11 9:37 [PATCH] lib/bb/event: improve handling of event queue on exit Paul Eggleton
2012-09-12 17:02 ` Chris Larson
2012-09-14 8:28 ` Richard Purdie [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=1347611317.9456.3.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
/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.