All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ed Bartosh <ed.bartosh@linux.intel.com>
To: bitbake-devel@lists.openembedded.org
Subject: [PATCH 0/2] Fix cooker log download button
Date: Wed,  7 Oct 2015 13:20:13 +0300	[thread overview]
Message-ID: <cover.1444213003.git.ed.bartosh@linux.intel.com> (raw)


* Retrieve a build's log file location directly from the file system,
as the one which is available at the time of the BuildStarted event
is incorrect.

* Hide the "Download build log" button for builds which fail early
(e.g. due to recipe parsing) and consequently have no cooker_log_path.


The following changes since commit 34399e5950509ffe978d9e6a31e91193d1bdcf0a:

  toaster: orm Machines filter don't pass self in as parameter (2015-10-06 20:08:50 -0700)

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib ed/toaster/submit/elliot/toaster/wrong_log-8373
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=ed/toaster/submit/elliot/toaster/wrong_log-8373

Elliot Smith (2):
  toaster: Manually retrieve log file location from filesystem
  toaster: Hide "Download build log" button if log doesn't exist

 bitbake/lib/bb/ui/toasterui.py                     | 31 +++++++++++++++++++++-
 .../toastergui/templates/builddashboard.html       |  4 ++-
 2 files changed, 33 insertions(+), 2 deletions(-)

--
Ed



             reply	other threads:[~2015-10-07 10:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-07 10:20 Ed Bartosh [this message]
2015-10-07 10:20 ` [PATCH 1/2] toaster: Manually retrieve log file location from filesystem Ed Bartosh
2015-10-11  7:07   ` Richard Purdie
2015-10-07 10:20 ` [PATCH 2/2] toaster: Hide "Download build log" button if log doesn't exist Ed Bartosh

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.1444213003.git.ed.bartosh@linux.intel.com \
    --to=ed.bartosh@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.