summaryrefslogtreecommitdiffstats
path: root/bitbake/lib/bb/runqueue.py
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2015-06-19 12:26:54 +0100
committerRichard Purdie <richard.purdie@linuxfoundation.org>2015-06-23 11:57:58 +0100
commit810bf0093a2488e861b361ac03a13b147964171a (patch)
treebe0161a15aafbae6ca1078c1309a20a65e3b741d /bitbake/lib/bb/runqueue.py
parent2ce9055e4fca3bfbdf8769d7a98650b4c2268887 (diff)
downloadpoky-810bf0093a2488e861b361ac03a13b147964171a.tar.gz
bitbake: runqueue: Handle BBHandledException correctly
If we see a BBHandledException in runqueue, the understanding is the system handled it, printing a log and traceback is just confusing. Therefore only print these in the cases where its an unknown/unhandled exception. (Bitbake rev: 29d28e22ce431c3d3aabdb88ff4d8cca67a1cfad) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'bitbake/lib/bb/runqueue.py')
-rw-r--r--bitbake/lib/bb/runqueue.py7
1 files changed, 7 insertions, 0 deletions
diff --git a/bitbake/lib/bb/runqueue.py b/bitbake/lib/bb/runqueue.py
index f1155f8f45..cc1aedfce7 100644
--- a/bitbake/lib/bb/runqueue.py
+++ b/bitbake/lib/bb/runqueue.py
@@ -1096,6 +1096,13 @@ class RunQueue:
1096 raise 1096 raise
1097 except SystemExit: 1097 except SystemExit:
1098 raise 1098 raise
1099 except bb.BBHandledException:
1100 try:
1101 self.teardown_workers()
1102 except:
1103 pass
1104 self.state = runQueueComplete
1105 raise
1099 except: 1106 except:
1100 logger.error("An uncaught exception occured in runqueue, please see the failure below:") 1107 logger.error("An uncaught exception occured in runqueue, please see the failure below:")
1101 try: 1108 try: