[bitbake-devel,0/1] v2: cooker.py and friends, switch to SanityCheck events

Submitted by Peter Seebach on Nov. 20, 2013, 11:26 p.m. | Patch ID: 62051


Message ID cover.1384989450.git.peter.seebach@windriver.com
State New
Headers show


git://git.yoctoproject.org/poky-contrib seebs/insanity_continued

Commit Message

Peter Seebach Nov. 20, 2013, 11:26 p.m.
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

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(-)