failures_lib: CompoundFailure should include textual tracebacks in its message
This makes errors easier to debug. For cases where textual tracebacks
are not needed (e.g. failure reason printed on the waterfall), we
explicitly exclude such information.
BUG=chromium:394820
TEST=`cbuildbot/run_tests`
Change-Id: Ifea8c2a48bf554d5fb33a581282cf52b135447e7
Reviewed-on: https://chromium-review.googlesource.com/208773
Tested-by: Yu-Ju Hong <yjhong@chromium.org>
Reviewed-by: Yu-Ju Hong <yjhong@chromium.org>
Commit-Queue: Yu-Ju Hong <yjhong@chromium.org>
diff --git a/scripts/cbuildbot.py b/scripts/cbuildbot.py
index 1ed20a2..b13593a 100644
--- a/scripts/cbuildbot.py
+++ b/scripts/cbuildbot.py
@@ -397,7 +397,7 @@
# If the build is marked as successful, but threw exceptions, that's a
# problem. Print the traceback for debugging.
if isinstance(ex, failures_lib.CompoundFailure):
- print ex.ToFullMessage()
+ print str(ex)
traceback.print_exc(file=sys.stdout)
raise