summaryrefslogtreecommitdiffstats
path: root/meta/recipes-core/eglibc
diff options
context:
space:
mode:
authorPaul Eggleton <paul.eggleton@linux.intel.com>2012-09-07 16:22:54 +0100
committerRichard Purdie <richard.purdie@linuxfoundation.org>2012-09-10 13:14:08 +0100
commit21816355c00eadb2273d61b456f06239ca300b47 (patch)
treee02423f9ae95bef7950a91335d769fe0ba86a135 /meta/recipes-core/eglibc
parent4d8ba9a0ec0afc2d14042ac0e153827b65a7428d (diff)
downloadpoky-21816355c00eadb2273d61b456f06239ca300b47.tar.gz
bitbake: cooker: fix handling of exceptions during exception handling
If an exception occurs during handling another exception we were getting a useless traceback such as the following, after which BitBake froze: ERROR: Command execution failed: Traceback (most recent call last): File "/home/user/poky/poky/bitbake/lib/bb/command.py", line 84, in runAsyncCommand self.cooker.updateCache() File "/home/user/poky/poky/bitbake/lib/bb/cooker.py", line 1207, in updateCache if not self.parser.parse_next(): File "/home/user/poky/poky/bitbake/lib/bb/cooker.py", line 1694, in parse_next logger.error('Unable to parse %s', value.recipe, AttributeError: 'exceptions.TypeError' object has no attribute 'recipe' Fix this to print an actual traceback of the exception and exit gracefully (well, as gracefully as possible under the circumstances). The general fix for [YOCTO #2977]. (Bitbake rev: 675b237a284dff84e972546774b69e2f89afb360) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-core/eglibc')
0 files changed, 0 insertions, 0 deletions