From c2852ea835a54ee967fd1e8cf3717844c338d2a1 Mon Sep 17 00:00:00 2001 From: Paul Eggleton Date: Thu, 29 May 2014 18:17:16 +0100 Subject: bitbake: utils: avoid printing traceback on ExpansionError during parsing If an ExpansionError occurs during better_exec() we should just raise it instead of printing the traceback, so that recipe errors (such as broken URLs in SRC_URI) are more easily comprehensible. (Bitbake rev: 5b0da8932c318813138c113d2bb20498145dbd42) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie --- bitbake/lib/bb/utils.py | 2 ++ 1 file changed, 2 insertions(+) (limited to 'bitbake/lib/bb/utils.py') diff --git a/bitbake/lib/bb/utils.py b/bitbake/lib/bb/utils.py index 1be1874cbc..ead5f366b0 100644 --- a/bitbake/lib/bb/utils.py +++ b/bitbake/lib/bb/utils.py @@ -357,6 +357,8 @@ def better_exec(code, context, text = None, realfile = ""): except bb.BBHandledException: # Error already shown so passthrough raise + except bb.data_smart.ExpansionError: + raise except Exception as e: (t, value, tb) = sys.exc_info() -- cgit v1.2.3-54-g00ecf