From 6b5d323b6c8960a0999dbafa0422fe127fd0fa97 Mon Sep 17 00:00:00 2001 From: Chris Larson Date: Thu, 2 Jun 2011 14:32:17 -0700 Subject: event: don't catch systemexit from handler execution This means that anyone firing an event can get a systemexit and result in their process exiting, which isn't ideal, but behaves the way it used to (in particular, ensures that a sanity check failure will halt the build). This should be revisited in the future. (Bitbake rev: d6a0ffdd583be3df734171d7e91d334f798a79ce) Signed-off-by: Chris Larson Signed-off-by: Richard Purdie --- bitbake/lib/bb/event.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'bitbake') diff --git a/bitbake/lib/bb/event.py b/bitbake/lib/bb/event.py index 9e64fe5c42..cbe49fd699 100644 --- a/bitbake/lib/bb/event.py +++ b/bitbake/lib/bb/event.py @@ -87,7 +87,7 @@ def fire_class_handlers(event, d): for name, handler in _handlers.iteritems(): try: execute_handler(name, handler, event, d) - except BaseException: + except Exception: continue ui_queue = [] -- cgit v1.2.3-54-g00ecf