From: Thierry Parmentelat <thierry.parmentelat@sophia.inria.fr>
Date: Thu, 24 Jun 2010 20:52:56 +0000 (+0200)
Subject: a few messages to help understand how all steps being OK can result in a build failure
X-Git-Tag: tests-5.0-7~6
X-Git-Url: http://git.onelab.eu/?a=commitdiff_plain;h=887d3f46aba48020a9d479fa7a23dc1f18826db6;p=tests.git

a few messages to help understand how all steps being OK can result in a build failure
---

diff --git a/system/TestMain.py b/system/TestMain.py
index ac6edd5..360f918 100755
--- a/system/TestMain.py
+++ b/system/TestMain.py
@@ -308,6 +308,7 @@ steps refer to a method in TestPlc or to a step_* module
         # do all steps on all plcs
         TRACE_FORMAT="TRACE: time=%(time)s status=%(status)s step=%(stepname)s plc=%(plcname)s force=%(force)s\n"
         for (stepname,method,force) in all_step_infos:
+            print "Entering step %(stepname)s with overall=%(overall_result)r"%locals()
             for (spec,obj) in all_plcs:
                 plcname=spec['name']
 
@@ -374,6 +375,7 @@ steps refer to a method in TestPlc or to a step_* module
                         trace.write(TRACE_FORMAT%locals())
                         trace.flush()
 
+        print "After last step, overall=%(overall_result)r"%locals()
         if self.options.trace_file and not self.options.dry_run:
             trace.close()
 
@@ -388,6 +390,7 @@ steps refer to a method in TestPlc or to a step_* module
             else:
                 return 1 
         except SystemExit:
+            print 'Caught SystemExit'
             raise
         except:
             traceback.print_exc()