From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH 0/8] Error message improvements
Date: Sun, 15 Jan 2012 10:07:16 +0000 [thread overview]
Message-ID: <1326622036.18815.11.camel@ted> (raw)
In-Reply-To: <cover.1326473488.git.paul.eggleton@linux.intel.com>
On Fri, 2012-01-13 at 17:01 +0000, Paul Eggleton wrote:
> A number of fixes to improve the readability of error messages,
> primarily for fetch errors, but will improve error output in other
> situations as well.
>
> (This supersedes the set of patches I sent a couple of days ago.)
>
> The changes (against Poky, but apply cleanly with -p2 against bitbake
> master) are available in the git repository at:
> git://git.yoctoproject.org/poky-contrib paule/errorhandling
> http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=paule/errorhandling
>
> Paul Eggleton (8):
> bitbake/knotty: don't count errors as warnings in summary
> bitbake/fetch2: improve error formatting for fetcher errors
> bitbake/runqueue: avoid "failed" in task summary if nothing did
> bitbake/fetch2: correctly decode exit signal/status
> bitbake/knotty: avoid printing full task log when error already
> printed
> bitbake/fetch2: reduce output for fetch failures
> bitbake/cooker: avoid printing stack trace for -b match error
> bitbake/knotty: print task failure summary
Merged to master, thanks. Some good improvements in there.
Cheers,
Richard
prev parent reply other threads:[~2012-01-15 10:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-13 17:01 [PATCH 0/8] Error message improvements Paul Eggleton
2012-01-13 17:01 ` [PATCH 1/8] bitbake/knotty: don't count errors as warnings in summary Paul Eggleton
2012-01-13 17:01 ` [PATCH 2/8] bitbake/fetch2: improve error formatting for fetcher errors Paul Eggleton
2012-01-13 17:01 ` [PATCH 3/8] bitbake/runqueue: avoid "failed" in task summary if nothing did Paul Eggleton
2012-01-13 17:01 ` [PATCH 4/8] bitbake/fetch2: correctly decode exit signal/status Paul Eggleton
2012-01-13 17:01 ` [PATCH 5/8] bitbake/knotty: avoid printing full task log when error already printed Paul Eggleton
2012-01-13 17:01 ` [PATCH 6/8] bitbake/fetch2: reduce output for fetch failures Paul Eggleton
2012-01-13 17:01 ` [PATCH 7/8] bitbake/cooker: avoid printing stack trace for -b match error Paul Eggleton
2012-01-13 17:01 ` [PATCH 8/8] bitbake/knotty: print task failure summary Paul Eggleton
2012-01-15 10:07 ` 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=1326622036.18815.11.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.