From: brian avery <brian.avery@intel.com>
To: toaster@yoctoproject.org
Cc: brian avery <brian.avery@intel.com>
Subject: [PATCH 0/3] toaster: allow builddir to be named other than build bug 9992 V2
Date: Tue, 7 Feb 2017 12:36:11 -0800 [thread overview]
Message-ID: <cover.1486499681.git.brian.avery@intel.com> (raw)
This pattchset fixes two bugs. The most important of which is in the sublject line.
9992 -> if we do oe-init-build-env cow, toaster would fail because it had the directory
name build hardcoded for toaster.sqlite. This patch moves the toaster.sqlite database to
TOASTER_DIR so that you can name your builddir whatever you'd like to.
11006-> the runbuilds process was printing out alot of debug and status messages to the
console. Since the console can also be used to run cli builds while toaster displays
their status, this was quite disconcerting. This patch redirects the output to
toaster_runbuilds.log.
-brian avery
The following changes since commit a624cf7f95c8cf4ff764cc997fd1db4601b97dcc:
oeqa/selftest/pkgdata: use m4 instead of bash (2017-02-07 14:50:10 +0000)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib bavery/toaster/9992-builddir-not-buildV5
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=bavery/toaster/9992-builddir-not-buildV5
brian avery (3):
toaster: put runbuilds output into a log file
toaster: move sqlite database to TOASTER_DIR
toaster: remove cut and paste cruft
bitbake/bin/toaster | 19 ++++++-------------
bitbake/lib/toaster/toastermain/settings.py | 3 +--
2 files changed, 7 insertions(+), 15 deletions(-)
--
1.9.1
next reply other threads:[~2017-02-07 20:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-07 20:36 brian avery [this message]
2017-02-07 20:36 ` [PATCH 1/3] toaster: put runbuilds output into a log file brian avery
2017-02-07 20:36 ` [PATCH 2/3] toaster: move sqlite database to TOASTER_DIR brian avery
2017-02-07 20:36 ` [PATCH 3/3] toaster: remove cut and paste cruft brian avery
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.1486499681.git.brian.avery@intel.com \
--to=brian.avery@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.