All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ed Bartosh <ed.bartosh@linux.intel.com>
To: toaster@yoctoproject.org
Subject: [PATCH 0/3] Pass BRBE to buildinfohelper as soon as it's set
Date: Tue,  8 Dec 2015 17:23:22 +0200	[thread overview]
Message-ID: <cover.1449587902.git.ed.bartosh@linux.intel.com> (raw)

Hi,

This patchset is a replacement of 3 patches that were rejected yesterday
by upstream.

It fixes 'hanging' builds in UI when build is failed on early stages (recipe
parsing or processing configuration).

The following changes since commit befaceb2873ff8c8cc791d48f0324442c15cbcdc:

  toaster: return back 'New project' button (2015-12-08 13:10:33 +0200)

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib ed/toaster/trigger-metadata-event
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=ed/toaster/trigger-metadata-event

Ed Bartosh (3):
  toaster: implement BitbakeController.triggerEvent
  toaster: trigger SetBRBE event
  toasterui: process SetBRBE event

 bitbake/lib/bb/ui/toasterui.py                          | 2 ++
 bitbake/lib/toaster/bldcontrol/bbcontroller.py          | 3 +++
 bitbake/lib/toaster/bldcontrol/localhostbecontroller.py | 3 +++
 3 files changed, 8 insertions(+)

--
Regards,
Ed



             reply	other threads:[~2015-12-08 15:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-08 15:23 Ed Bartosh [this message]
2015-12-08 15:23 ` [PATCH 1/3] toaster: implement BitbakeController.triggerEvent Ed Bartosh
2015-12-08 15:23 ` [PATCH 2/3] toaster: trigger SetBRBE event Ed Bartosh
2015-12-08 15:23 ` [PATCH 3/3] toasterui: process " Ed Bartosh
2015-12-08 16:12 ` [PATCH 0/3] Pass BRBE to buildinfohelper as soon as it's set Richard Purdie
2015-12-09 14:52   ` Michael Wood
  -- strict thread matches above, loose matches on Subject: below --
2015-12-09 14:25 Michael Wood

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.1449587902.git.ed.bartosh@linux.intel.com \
    --to=ed.bartosh@linux.intel.com \
    --cc=toaster@yoctoproject.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.