0.6.7.12: punted various multi-proc code, started cleaning up dynamic-space

[sbcl.git] / tests / run-tests.sh

diff --git a/tests/run-tests.sh b/tests/run-tests.sh
index 366eba1..de63a75 100644 (file)
--- a/tests/run-tests.sh
+++ b/tests/run-tests.sh
@@ -3,17 +3,28 @@
 # Run the regression tests in this directory.
 
 # how we invoke SBCL
-sbcl=${1:-sbcl --noprint --noprogrammer}
+sbcl=${1:-sbcl --noinform --noprint --noprogrammer}
+
+# "Ten four" is the closest numerical slang I can find to "OK", so
+# it's the return value we expect from a successful test.
+tenfour () {
+    if [ $? = 104 ]; then
+       echo ok
+    else
+       echo test failed: $?
+       return 1
+    fi
+}
 
 # *.pure.lisp files are ordinary Lisp code with no side effects,
 # and we can run them all in a single Lisp process.
-(for f in *.pure.lisp; do echo \"$f\"; done) | $sbcl < pure.lisp
+(for f in *.pure.lisp; do echo \"$f\"; done) | $sbcl ; tenfour
 
 # *.impure.lisp files are Lisp code with side effects (e.g. doing DEFSTRUCT
 # or DEFTYPE or DEFVAR). Each one needs to be run as a separate
 # invocation of Lisp.
 for f in *.impure.lisp; do
-    echo $f | $sbcl < pure.lisp
+    echo $f | $sbcl ; tenfour
 done
 
 # *.test.sh files are scripts to test stuff, typically stuff which can't
@@ -21,11 +32,11 @@ done
 # may be associated with other files foo*, e.g. foo.lisp, foo-1.lisp,
 # or foo.pl.
 for f in *.test.sh; do
-    sh $f || exit failed test $f
+    sh $f ; tenfour
 done
 
 # *.assertoids files contain ASSERTOID statements to test things
 # interpreted and at various compilation levels.
 for f in *.assertoids; do
-    echo "(load \"$f\")" | $sbcl --eval '(load "assertoid.lisp")'
+    echo "(load \"$f\")" | $sbcl --eval '(load "assertoid.lisp")' ; tenfour
 done