3 # Run the regression tests in this directory.
6 sbcl=${1:-../src/runtime/sbcl --core ../output/sbcl.core --noinform --noprint --noprogrammer}
8 # "Ten four" is the closest numerical slang I can find to "OK", so
9 # it's the return value that we expect from a successful test.
19 # *.pure.lisp files are ordinary Lisp code with no side effects,
20 # and we can run them all in a single Lisp process.
21 echo //running '*.pure.lisp' tests
22 echo //i.e. *.pure.lisp
23 (for f in *.pure.lisp; do
26 echo " (progn (format t \"//running $f test~%\") (load \"$f\"))"
28 echo " (sb-ext:quit :unix-status 104))"
29 done) | $sbcl ; tenfour
31 # *.impure.lisp files are Lisp code with side effects (e.g. doing DEFSTRUCT
32 # or DEFTYPE or DEFVAR). Each one needs to be run as a separate
34 echo //running '*.impure.lisp' tests
35 for f in *.impure.lisp; do
37 echo //running $f test
38 echo "(load \"$f\")" | $sbcl ; tenfour
42 # *.test.sh files are scripts to test stuff, typically stuff which can't
43 # so easily be tested within Lisp itself. A file foo.test.sh
44 # may be associated with other files foo*, e.g. foo.lisp, foo-1.lisp,
46 echo //running '*.test.sh' tests
47 for f in *.test.sh; do
49 echo //running $f test
54 # *.assertoids files contain ASSERTOID statements to test things
55 # interpreted and at various compilation levels.
56 echo //running '*.assertoids' tests
57 for f in *.assertoids; do
59 echo //running $f test
60 echo "(load \"$f\")" | $sbcl --eval '(load "assertoid.lisp")' ; tenfour