[Piglit] [PATCH 3/4] framework: Recognise more crashes return codes.

jfonseca at vmware.com jfonseca at vmware.com
Mon Jun 9 08:39:21 PDT 2014


From: José Fonseca <jfonseca at vmware.com>

>From what I gathered, both on Linux and Windows, uncaught
exceptions/signals lead to a negative return code.
---
 framework/exectest.py | 16 +---------------
 1 file changed, 1 insertion(+), 15 deletions(-)

diff --git a/framework/exectest.py b/framework/exectest.py
index 5cfa05e..a833066 100644
--- a/framework/exectest.py
+++ b/framework/exectest.py
@@ -155,21 +155,7 @@ class Test(object):
         self.result['result'] = 'fail'
         self.interpret_result()
 
-        crash_codes = [
-            # Unix: terminated by a signal
-            -5,   # SIGTRAP
-            -6,   # SIGABRT
-            -8,   # SIGFPE  (Floating point exception)
-            -10,  # SIGUSR1
-            -11,  # SIGSEGV (Segmentation fault)
-            # Windows:
-            # EXCEPTION_ACCESS_VIOLATION (0xc0000005):
-            -1073741819,
-            # EXCEPTION_INT_DIVIDE_BY_ZERO (0xc0000094):
-            -1073741676
-        ]
-
-        if self.result['returncode'] in crash_codes:
+        if self.result['returncode'] < 0:
             self.result['result'] = 'crash'
         elif self.result['returncode'] != 0 and self.result['result'] == 'pass':
             self.result['result'] = 'warn'
-- 
1.9.1



More information about the Piglit mailing list