All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Wood <michael.g.wood@intel.com>
To: bitbake-devel@lists.openembedded.org
Subject: [PATCH 0/3] toaster: Fix error thrown by command line builds project page
Date: Wed, 14 Oct 2015 14:59:13 +0100	[thread overview]
Message-ID: <cover.1444830820.git.michael.g.wood@intel.com> (raw)


This patch series fixes an exception being thrown when viewing
the default "command line builds" project while a bitbake command line
build is running.

It also modifies and cleans up the toaster startup script so that
the bldcontrol migrations are applied in analysis mode, as well as
in managed mode. This should help prevent other errors which may
occur in analysis mode due to missing database tables.


Available in the git repository at:

  git://git.yoctoproject.org/poky-contrib michaelw/submit/elliot/toaster/cli_builds_error-8277
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=michaelw/submit/elliot/toaster/cli_builds_error-8277

Elliot Smith (3):
  toaster: Always run bldcontrol migrations
  toaster: Check whether buildrequest exists before using it
  toaster: Test that exception isn't thrown by project page

 bin/toaster                     | 56 ++++++++++++++++++++++++++++-------------
 lib/toaster/orm/models.py       | 20 +++++++++++++--
 lib/toaster/toastergui/tests.py | 30 ++++++++++++++++++++++
 3 files changed, 87 insertions(+), 19 deletions(-)

-- 
2.1.4



             reply	other threads:[~2015-10-14 13:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-14 13:59 Michael Wood [this message]
2015-10-14 14:43 ` [PATCH 1/3] toaster: Always run bldcontrol migrations Michael Wood
2015-10-14 14:43 ` [PATCH 2/3] toaster: Check whether buildrequest exists before using it Michael Wood
2015-10-14 14:43 ` [PATCH 3/3] toaster: Test that exception isn't thrown by project page 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.1444830820.git.michael.g.wood@intel.com \
    --to=michael.g.wood@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.