[Lldb-commits] [lldb] r175656 - Fix a bug that causes dotest.py to exit with a passing exit-code, even if some tests fail

Daniel Malea daniel.malea at intel.com
Wed Feb 20 12:12:11 PST 2013


Author: dmalea
Date: Wed Feb 20 14:12:11 2013
New Revision: 175656

URL: http://llvm.org/viewvc/llvm-project?rev=175656&view=rev
Log:
Fix a bug that causes dotest.py to exit with a passing exit-code, even if some tests fail
- occurs when multiple compilers/architectures are tested (via -C or -A flags)



Modified:
    lldb/trunk/test/dotest.py

Modified: lldb/trunk/test/dotest.py
URL: http://llvm.org/viewvc/llvm-project/lldb/trunk/test/dotest.py?rev=175656&r1=175655&r2=175656&view=diff
==============================================================================
--- lldb/trunk/test/dotest.py (original)
+++ lldb/trunk/test/dotest.py Wed Feb 20 14:12:11 2013
@@ -227,6 +227,7 @@ testdirs = [ sys.path[0] ]
 # Separator string.
 separator = '-' * 70
 
+failed = False
 
 def usage(parser):
     parser.print_help()
@@ -1516,6 +1517,7 @@ for ia in range(len(archs) if iterArchs
                                                   failfast=failfast,
                                                   resultclass=LLDBTestResult).run(suite)
 
+        failed = failed or not result.wasSuccessful()
 
 if sdir_has_content and not parsable:
     sys.stderr.write("Session logs for test failures/errors/unexpected successes"
@@ -1537,4 +1539,4 @@ if ("LLDB_TESTSUITE_FORCE_FINISH" in os.
     subprocess.Popen(["/bin/sh", "-c", "kill %s; exit 0" % (os.getpid())])
 
 # Exiting.
-sys.exit(not result.wasSuccessful())
+sys.exit(failed)





More information about the lldb-commits mailing list