All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: bitbake-devel@lists.openembedded.org
Subject: [PATCH 0/3] Fixes for scenequeue task failure
Date: Thu,  1 Mar 2012 14:57:34 +0000	[thread overview]
Message-ID: <cover.1330613733.git.paul.eggleton@linux.intel.com> (raw)

After some more extensive testing, fix some regressions in scenequeue
task failure handling caused by one of my earlier commits.

The following changes since commit 8f07bdc0a42dd7a7c3acf5d1b13220dbc98c8017:

  image_types_uboot: Update to work after recent image_types changes (2012-02-29 18:25:03 +0000)

are available in the git repository at:
  git://git.yoctoproject.org/poky-contrib paule/bb-sceneqtaskfail
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=paule/bb-sceneqtaskfail

Paul Eggleton (3):
  bitbake/runqueue: fix python error on scenequeue task failure
  bitbake/uihelper: restore line to record failed normal tasks
  bitbake/build: report TaskFailedSilent events as "Failed"

 bitbake/lib/bb/build.py       |    9 ++++++++-
 bitbake/lib/bb/runqueue.py    |    3 +--
 bitbake/lib/bb/ui/uihelper.py |    7 ++++++-
 3 files changed, 15 insertions(+), 4 deletions(-)

-- 
1.7.5.4




             reply	other threads:[~2012-03-01 15:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-01 14:57 Paul Eggleton [this message]
2012-03-01 14:57 ` [PATCH 1/3] bitbake/runqueue: fix python error on scenequeue task failure Paul Eggleton
2012-03-01 14:57 ` [PATCH 2/3] bitbake/uihelper: restore line to record failed normal tasks Paul Eggleton
2012-03-01 14:57 ` [PATCH 3/3] bitbake/build: report TaskFailedSilent events as "Failed" Paul Eggleton
2012-03-01 15:26 ` [PATCH 0/3] Fixes for scenequeue task failure Richard Purdie

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=cover.1330613733.git.paul.eggleton@linux.intel.com \
    --to=paul.eggleton@linux.intel.com \
    --cc=bitbake-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.