summaryrefslogtreecommitdiffstats
path: root/lib/bb/server/process.py
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2015-06-19 12:26:25 +0100
committerRichard Purdie <richard.purdie@linuxfoundation.org>2015-06-19 22:43:48 +0100
commitd88ecc2bc44dce8fd92ca3a2c0fd4124a5e464fa (patch)
treeab6efb56ccd39f999604ebaf350674e56501489b /lib/bb/server/process.py
parentad286d6fed7a580bec36a92c7b7e205322ac407b (diff)
downloadbitbake-contrib-d88ecc2bc44dce8fd92ca3a2c0fd4124a5e464fa.tar.gz
server/process: Don't log BBHandledException
If we see a BBHandledException in the idle handler, 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. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'lib/bb/server/process.py')
-rw-r--r--lib/bb/server/process.py5
1 files changed, 3 insertions, 2 deletions
diff --git a/lib/bb/server/process.py b/lib/bb/server/process.py
index c9286ddba..ef3ee57aa 100644
--- a/lib/bb/server/process.py
+++ b/lib/bb/server/process.py
@@ -144,8 +144,9 @@ class ProcessServer(Process, BaseImplServer):
fds = fds + retval
except SystemExit:
raise
- except Exception:
- logger.exception('Running idle function')
+ except Exception as exc:
+ if not isinstance(exc, bb.BBHandledException):
+ logger.exception('Running idle function')
del self._idlefuns[function]
self.quit = True