Fix run-tests.sh on Solaris.

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

diff --git a/tests/run-tests.sh b/tests/run-tests.sh
old mode 100644 (file)
new mode 100755 (executable)
index 809ec8f..ed1b498
--- a/tests/run-tests.sh
+++ b/tests/run-tests.sh
@@ -1,62 +1,55 @@
 #!/bin/sh
 
-# Run the regression tests in this directory.
+# This software is part of the SBCL system. See the README file for
+# more information.
+#
+# While most of SBCL is derived from the CMU CL system, the test
+# files (like this one) were written from scratch after the fork
+# from CMU CL.
+#
+# This software is in the public domain and is provided with
+# absolutely no warranty. See the COPYING and CREDITS files for
+# more information.
 
-# how we invoke SBCL
-sbcl=${1:-../src/runtime/sbcl --core ../output/sbcl.core --noinform --noprint --noprogrammer}
+if [ "$1" = "--help" ]; then
+    cat <<EOF
+Run the regression tests in this directory.
+
+Usage: $0 [OPTIONS] [files]
+
+Options:
+
+  --break-on-failure            Break into the debugger when a test fails
+                                unexpectedly
+  --break-on-expected-failure   Break into the debugger when any test fails
+  --report-skipped-tests        Include tests :skipped-on target SBCL in
+                                the test report.
+  --no-color                    Disable coloring of results. 
+
+If no test files are specified, runs all tests.
+EOF
+    exit 0
+fi
+
+
+. ./subr.sh
+
+echo /running tests on \'$SBCL_RUNTIME --core $SBCL_CORE $SBCL_ARGS\'
 
-# "Ten four" is the closest numerical slang I can find to "OK", so
-# it's the return value that we expect from a successful test.
 tenfour () {
-    if [ $? = 104 ]; then
-       echo ok
+    if [ $1 = $EXIT_TEST_WIN ]; then
+        echo ok
     else
-       echo test failed: $?
-       exit 1
+        echo test failed, expected $EXIT_TEST_WIN return code, got $1
+        exit 1
     fi
 }
+set +u
+run_sbcl \
+    --eval '(with-compilation-unit () (load "run-tests.lisp"))' \
+    --eval '(run-tests::run-all)' $*
 
-# *.pure.lisp files are ordinary Lisp code with no side effects,
-# and we can run them all in a single Lisp process.
-echo //running '*.pure.lisp' tests
-echo //i.e. *.pure.lisp
-(for f in *.pure.lisp; do
-    echo "(progn"
-    if [ -f $f ]; then
-        echo "  (progn (format t \"//running $f test~%\") (load \"$f\"))"
-    fi
-    echo "  (sb-ext:quit :unix-status 104))"
-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.
-echo //running '*.impure.lisp' tests
-for f in *.impure.lisp; do
-    if [ -f $f ]; then
-        echo //running $f test
-        echo "(load \"$f\")" | $sbcl ; tenfour
-    fi
-done
-
-# *.test.sh files are scripts to test stuff, typically stuff which can't
-# so easily be tested within Lisp itself. A file foo.test.sh
-# may be associated with other files foo*, e.g. foo.lisp, foo-1.lisp,
-# or foo.pl.
-echo //running '*.test.sh' tests
-for f in *.test.sh; do
-    if [ -f $f ]; then
-       echo //running $f test
-       sh $f ; tenfour
-    fi
-done
-
-# *.assertoids files contain ASSERTOID statements to test things
-# interpreted and at various compilation levels.
-echo //running '*.assertoids' tests
-for f in *.assertoids; do
-    if [ -f $f ]; then
-       echo //running $f test
-       echo "(load \"$f\")" | $sbcl --eval '(load "assertoid.lisp")' ; tenfour
-    fi
-done
+tenfour $?
+
+echo '//apparent success (reached end of run-tests.sh normally)'
+date