Unless --failfast is specified, all test files should be executed.

This commit is contained in:
Richard Frith-Macdonald 2022-02-16 09:28:34 +00:00
parent 0c837c086b
commit fd76f00ab8
2 changed files with 22 additions and 4 deletions

View file

@ -1,3 +1,10 @@
2022-02-16 Richard Frith-Macdonald <rfm@gnu.org>
* TestFramework/gnustep-tests.in:
Fix bug introduced in rewrite for parallelisation: we were getting
immediate end of testing when one file failed, but that behavior
should only occur when --failfast is specified.
2022-01-26 Richard Frith-Macdonald <rfm@gnu.org>
* TestFramework/README:

View file

@ -435,7 +435,8 @@ run_test ()
fi
fi
if test $? != 0
result=$?
if test $result != 0
then
if test -r $TESTFILE.abort
then
@ -474,7 +475,14 @@ run_test_log ()
else
run_test $TESTFILE $TESTNAME >> $TESTLOG 2>&1
fi
RUNEXIT=$?
result=$?
if test "$result" != "0"
then
if test "$GSTESTMODE" = "failfast"
then
RUNEXIT=1
fi
fi
}
proc_test_log ()
@ -499,7 +507,10 @@ proc_test_log ()
echo
echo $dir/$TESTFILE:
extract $GSTESTSUM.tmp "^Failed build:" "^Failed file:" "^Failed set:" "^Failed test:" "^Skipped set:"
RUNEXIT=1
if test "$GSTESTMODE" = "failfast"
then
RUNEXIT=1
fi
else
RUNEXIT=0
fi
@ -771,7 +782,7 @@ ${tmp}_OBJC_FILES=$TESTFILE"
proc_test_log $TESTFILE $TESTNAME test_$i.out test_$i.err
if test "$RUNEXIT" != "0"
then
break
break
fi
((i+=1))
fi