[PATCH] tester: Expand special case for minimum.exe

Kinsey Moore kinsey.moore at oarcorp.com
Wed May 26 13:52:06 UTC 2021


The minimum.exe test case is expected to fail as an "invalid" test in
the tester since it is completely stripped down and does not output the
normal test header and footer. When fatal error detection support was
added, this caught minimum.exe and started flagging it as "fatal"
instead of "invalid". The special-case detection of minimum.exe only
matched on "invalid" results and not "fatal" results and so began
flagging minimum.exe as an actual failure.

This change adds the special-case handling to the "fatal" test state
handling.
---
 tester/rt/report.py | 9 +++++++--
 1 file changed, 7 insertions(+), 2 deletions(-)

diff --git a/tester/rt/report.py b/tester/rt/report.py
index 0e19edc..1341f4f 100644
--- a/tester/rt/report.py
+++ b/tester/rt/report.py
@@ -194,8 +194,13 @@ class report(object):
                         status = 'passed'
                         self.passed += 1
                 elif fatal:
-                    status = 'fatal-error'
-                    self.failed += 1
+                    exe_name = path.basename(name).split('.')[0]
+                    if exe_name in test_fail_excludes:
+                        status = 'passed'
+                        self.passed += 1
+                    else:
+                        status = 'fatal-error'
+                        self.failed += 1
                 elif timeout:
                     status = 'timeout'
                     self.timeouts += 1
-- 
2.20.1



More information about the devel mailing list