From: Peter Seebach <peter.seebach@windriver.com>
To: <bitbake-devel@lists.openembedded.org>
Subject: [PATCH 0/1] v2: cooker.py and friends, switch to SanityCheck events
Date: Wed, 20 Nov 2013 17:26:22 -0600 [thread overview]
Message-ID: <cover.1384989450.git.peter.seebach@windriver.com> (raw)
This is probably a little off, but it's maybe worth a try. This
patch updates the mechanism used for sanity check events. It will
result in sanity checks being run twice, probably, without a
corresponding oe-core change, but shouldn't be otherwise harmful.
The intent is to get away from the idea that sanity checks are an
unintended and barely-documented side-effect of ConfigParsed, and
to introduce the idea that bitbake might have insights into whether
it wants sanity checks to be fatal.
The use-events stuff is related to how oe-core was doing this; it
assumed that it should use bb.event.SanityChecksFailed() instead of
printing a message if it got a SanityCheck event, and I'd rather not
change the behavior that much right now.
The following changes since commit 67b752993a2c64cba9ccc4fa662f0bddf081e74a:
toasterui: fix typo (2013-11-20 14:06:42 +0000)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib seebs/insanity_continued
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=seebs/insanity-continued
Peter Seebach (1):
cooker.py and friends: Convert to using Sanity Check events.
lib/bb/cooker.py | 2 ++
lib/bb/cookerdata.py | 10 ++++++++++
lib/bb/event.py | 4 ++++
lib/bb/ui/knotty.py | 1 +
4 files changed, 17 insertions(+), 0 deletions(-)
next reply other threads:[~2013-11-20 23:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-20 23:26 Peter Seebach [this message]
2013-11-20 23:26 ` [PATCH 1/1] cooker.py and friends: Convert to using Sanity Check events Peter Seebach
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.1384989450.git.peter.seebach@windriver.com \
--to=peter.seebach@windriver.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.