tests/run-tests.sh

   1 #!/bin/sh
   2
   3 # Run the regression tests in this directory.
   4
   5 # This software is part of the SBCL system. See the README file for
   6 # more information.
   7 #
   8 # While most of SBCL is derived from the CMU CL system, the test
   9 # files (like this one) were written from scratch after the fork
  10 # from CMU CL.
  11 #
  12 # This software is in the public domain and is provided with
  13 # absolutely no warranty. See the COPYING and CREDITS files for
  14 # more information.
  15
  16 # how we invoke SBCL in the tests
  17 #
  18 # Until sbcl-0.6.12.8, the shell variable SBCL was bound to a relative
  19 # pathname, but now we take care to bind it to an absolute pathname (still
  20 # generated relative to `pwd` in the tests/ directory) so that tests
  21 # can chdir before invoking SBCL and still work.
  22 sbclstem=`pwd`/../src/runtime/sbcl
  23 SBCL="${1:-$sbclstem --core `pwd`/../output/sbcl.core --noinform --sysinit /dev/null --userinit /dev/null --noprint --disable-debugger}"
  24 export SBCL
  25 echo /running tests on SBCL=\'$SBCL\'
  26 # more or less like SBCL, but without enough grot removed that appending
  27 # a --core command line argument works
  28 #
  29 # (KLUDGE: and also without any magic to suppress --userinit and
  30 # --sysinit, so if you use it in a test, you need to add those
  31 # yourself if you want things to be clean. If many tests start using
  32 # this, we can redo it as a shell function or something so that the
  33 # magic can be done once and only once.)
  34 SBCL_ALLOWING_CORE=${1:-$sbclstem}
  35 export SBCL_ALLOWING_CORE
  36 echo /with SBCL_ALLOWING_CORE=\'$SBCL_ALLOWING_CORE\'
  37
  38 # "Ten four" is the closest numerical slang I can find to "OK", so
  39 # it's the Unix status value that we expect from a successful test.
  40 # (Of course, zero is the usual success value, but we don't want to
  41 # use that because SBCL returns that by default, so we might think
  42 # we passed a test when in fact some error caused us to exit SBCL
  43 # in a weird unexpected way. In contrast, 104 is unlikely to be
  44 # returned unless we exit through the intended explicit "test
  45 # successful" path.
  46 tenfour () {
  47     if [ $? = 104 ]; then
  48         echo ok
  49     else
  50         echo test failed, expected 104 return code, got $?
  51         exit 1
  52     fi
  53 }
  54
  55 # *.pure.lisp files are ordinary Lisp code with no side effects,
  56 # and we can run them all in a single Lisp process.
  57 echo //running '*.pure.lisp' tests
  58 echo //i.e. *.pure.lisp
  59 (
  60 echo "(progn"
  61 for f in *.pure.lisp; do
  62     if [ -f $f ]; then
  63         echo "  (progn (format t \"//running $f test~%\") (load \"$f\"))"
  64     fi
  65 done
  66 echo "  (sb-ext:quit :unix-status 104)) ; Return status=success."
  67 ) | $SBCL ; tenfour
  68
  69 # *.impure.lisp files are Lisp code with side effects (e.g. doing
  70 # DEFSTRUCT or DEFTYPE or DEFVAR, or messing with the read table).
  71 # Each one should be LOADed in a separate invocation of Lisp, so
  72 # that we don't need to worry about them interfering with each
  73 # other.
  74 echo //running '*.impure.lisp' tests
  75 for f in *.impure.lisp; do
  76     if [ -f $f ]; then
  77         echo //running $f test
  78         echo "(load \"$f\")" | $SBCL ; tenfour
  79     fi
  80 done
  81
  82 # *.test.sh files are scripts to test stuff, typically stuff which
  83 # can't so easily be tested within Lisp itself. A file foo.test.sh
  84 # may be associated with other files foo*, e.g. foo.lisp, foo-1.lisp,
  85 # or foo.pl.
  86 echo //running '*.test.sh' tests
  87 for f in *.test.sh; do
  88     if [ -f $f ]; then
  89         echo //running $f test
  90         sh $f "$SBCL"; tenfour
  91     fi
  92 done
  93
  94 # *.assertoids files contain ASSERTOID statements to test things
  95 # interpreted and at various compilation levels.
  96 echo //running '*.assertoids' tests
  97 for f in *.assertoids; do
  98     if [ -f $f ]; then
  99         echo //running $f test
 100         echo "(load \"$f\")" | $SBCL --eval '(load "assertoid.lisp")' ; tenfour
 101     fi
 102 done
 103
 104 # *.pure-cload.lisp files want to be compiled, then loaded. They
 105 # can all be done in the same invocation of Lisp.
 106 echo //running '*.pure-cload.lisp' tests
 107 for f in *.pure-cload.lisp; do
 108     # (Actually here we LOAD each one into a separate invocation
 109     # of Lisp just because I haven't figured out a concise way
 110     # to LOAD them all into the same Lisp.)
 111     if [ -f $f ]; then
 112         echo //running $f test
 113         $SBCL <<EOF ; tenfour
 114                 (compile-file "$f")
 115                 (progn
 116                   (unwind-protect
 117                   (load *)
 118                    (ignore-errors (delete-file (compile-file-pathname "$f"))))
 119                   (sb-ext:quit :unix-status 104))
 120 EOF
 121     fi
 122 done
 123
 124 # *.impure-cload.lisp files want to be compiled, then loaded. They
 125 # can have side effects, so each one should be done in a separate
 126 # invocation of Lisp so that they don't interfere.
 127 echo //running '*.impure-cload.lisp' tests
 128 for f in *.impure-cload.lisp; do
 129     if [ -f $f ]; then
 130         echo //running $f test
 131         $SBCL <<EOF ; tenfour
 132                 (compile-file "$f")
 133                 (progn
 134                   (unwind-protect
 135                   (load *)
 136                    (ignore-errors (delete-file (compile-file-pathname "$f"))))
 137                   (sb-ext:quit :unix-status 104))
 138 EOF
 139     fi
 140 done
 141
 142 # (*.before-xc.lisp and *.after-xc.lisp files aren't handled in this
 143 # script at all. They're tests intended to run in the cross-compiler,
 144 # so that some functionality can be tested even when cold init doesn't
 145 # work.)
 146
 147 echo '//apparent success (reached end of run-tests.sh normally)'
 148 date