X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;f=tests%2Frun-tests.sh;h=debc22ab2e1816f3ba2cd9634ccd981e383cee97;hb=1a3143cca7d6678c094b6bacc485e8531808ea59;hp=40549f27d00b07c68888f70b2229b12ed233ea23;hpb=f2aa2d01b8d69f1c7bff18f86279d4f1018fe127;p=sbcl.git diff --git a/tests/run-tests.sh b/tests/run-tests.sh index 40549f2..debc22a 100644 --- a/tests/run-tests.sh +++ b/tests/run-tests.sh @@ -1,6 +1,13 @@ #!/bin/sh # Run the regression tests in this directory. +# +# Usage: run-tests.sh [--break-on-failure] [--break-on-expected-failure] [files] +# --break-on-failure Break into the debugger when a test fails +# unexpectedly +# --break-on-expected-failure Break into the debugger when any test fails +# +# If no test files are specified, runs all tests. # This software is part of the SBCL system. See the README file for # more information. @@ -8,13 +15,45 @@ # 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 in the tests -export SBCL="${1:-../src/runtime/sbcl --core ../output/sbcl.core --noinform --sysinit /dev/null --userinit /dev/null --noprint --noprogrammer}" +# +# Until sbcl-0.6.12.8, the shell variable SBCL was bound to a relative +# pathname, but now we take care to bind it to an absolute pathname (still +# generated relative to `pwd` in the tests/ directory) so that tests +# can chdir before invoking SBCL and still work. +. ../sbcl-pwd.sh +sbcl_pwd + +SBCL_HOME=$SBCL_PWD/../contrib +export SBCL_HOME +sbclstem=$SBCL_PWD/../src/runtime/sbcl + +SBCL="$sbclstem --core $SBCL_PWD/../output/sbcl.core --noinform --sysinit /dev/null --userinit /dev/null --noprint --disable-debugger" +export SBCL +echo /running tests on SBCL=\'$SBCL\' +# more or less like SBCL, but without enough grot removed that appending +# a --core command line argument works +# +# (KLUDGE: and also without any magic to suppress --userinit and +# --sysinit, so if you use it in a test, you need to add those +# yourself if you want things to be clean. If many tests start using +# this, we can redo it as a shell function or something so that the +# magic can be done once and only once.). Not used in this file, but +# exists for the benefit of the *.test.sh files that can be started by +# run-tests.lisp +SBCL_ALLOWING_CORE=$sbclstem +export SBCL_ALLOWING_CORE +echo /with SBCL_ALLOWING_CORE=\'$SBCL_ALLOWING_CORE\' + +LANG=C +LC_ALL=C +export LANG +export LC_ALL # "Ten four" is the closest numerical slang I can find to "OK", so # it's the Unix status value that we expect from a successful test. @@ -25,96 +64,18 @@ export SBCL="${1:-../src/runtime/sbcl --core ../output/sbcl.core --noinform --sy # returned unless we exit through the intended explicit "test # successful" path. tenfour () { - if [ $? = 104 ]; then - echo ok + if [ $1 = 104 ]; then + echo ok else - echo test failed: $? - exit 1 + echo test $2 failed, expected 104 return code, got $1 + exit 1 fi } -# *.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 -( -echo "(progn" -for f in *.pure.lisp; do - if [ -f $f ]; then - echo " (progn (format t \"//running $f test~%\") (load \"$f\"))" - fi -done -echo " (sb-ext:quit :unix-status 104)) ; Return status=success." -) | $SBCL ; tenfour - -# *.impure.lisp files are Lisp code with side effects (e.g. doing -# DEFSTRUCT or DEFTYPE or DEFVAR, or messing with the read table). -# Each one should be LOADed in a separate invocation of Lisp, so -# that we don't need to worry about them interfering with each -# other. -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 "$SBCL"; 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 - -# *.pure-cload.lisp files want to be compiled, then loaded. They -# can all be done in the same invocation of Lisp. -echo //running '*.pure-cload.lisp' tests -for f in *.pure-cload.lisp; do - # (Actually here we LOAD each one into a separate invocation - # of Lisp just because I haven't figured out a concise way - # to LOAD them all into the same Lisp.) - if [ -f $f ]; then - echo //running $f test - $SBCL <