3 # Run the regression tests in this directory.
5 # This software is part of the SBCL system. See the README file for
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
12 # This software is in the public domain and is provided with
13 # absolutely no warranty. See the COPYING and CREDITS files for
16 # how we invoke SBCL in the tests
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 export SBCL="${1:-`pwd`/../src/runtime/sbcl --core `pwd`/../output/sbcl.core --noinform --sysinit /dev/null --userinit /dev/null --noprint --noprogrammer}"
23 echo /running tests on SBCL=\'$SBCL\'
25 # "Ten four" is the closest numerical slang I can find to "OK", so
26 # it's the Unix status value that we expect from a successful test.
27 # (Of course, zero is the usual success value, but we don't want to
28 # use that because SBCL returns that by default, so we might think
29 # we passed a test when in fact some error caused us to exit SBCL
30 # in a weird unexpected way. In contrast, 104 is unlikely to be
31 # returned unless we exit through the intended explicit "test
37 echo test failed, expected 104 return code, got $?
42 # *.pure.lisp files are ordinary Lisp code with no side effects,
43 # and we can run them all in a single Lisp process.
44 echo //running '*.pure.lisp' tests
45 echo //i.e. *.pure.lisp
48 for f in *.pure.lisp; do
50 echo " (progn (format t \"//running $f test~%\") (load \"$f\"))"
53 echo " (sb-ext:quit :unix-status 104)) ; Return status=success."
56 # *.impure.lisp files are Lisp code with side effects (e.g. doing
57 # DEFSTRUCT or DEFTYPE or DEFVAR, or messing with the read table).
58 # Each one should be LOADed in a separate invocation of Lisp, so
59 # that we don't need to worry about them interfering with each
61 echo //running '*.impure.lisp' tests
62 for f in *.impure.lisp; do
64 echo //running $f test
65 echo "(load \"$f\")" | $SBCL ; tenfour
69 # *.test.sh files are scripts to test stuff, typically stuff which
70 # can't so easily be tested within Lisp itself. A file foo.test.sh
71 # may be associated with other files foo*, e.g. foo.lisp, foo-1.lisp,
73 echo //running '*.test.sh' tests
74 for f in *.test.sh; do
76 echo //running $f test
77 sh $f "$SBCL"; tenfour
81 # *.assertoids files contain ASSERTOID statements to test things
82 # interpreted and at various compilation levels.
83 echo //running '*.assertoids' tests
84 for f in *.assertoids; do
86 echo //running $f test
87 echo "(load \"$f\")" | $SBCL --eval '(load "assertoid.lisp")' ; tenfour
91 # *.pure-cload.lisp files want to be compiled, then loaded. They
92 # can all be done in the same invocation of Lisp.
93 echo //running '*.pure-cload.lisp' tests
94 for f in *.pure-cload.lisp; do
95 # (Actually here we LOAD each one into a separate invocation
96 # of Lisp just because I haven't figured out a concise way
97 # to LOAD them all into the same Lisp.)
99 echo //running $f test
100 $SBCL <<EOF ; tenfour
105 (ignore-errors (delete-file (compile-file-pathname "$f"))))
106 (sb-ext:quit :unix-status 104))
111 # *.impure-cload.lisp files want to be compiled, then loaded. They
112 # can have side effects, so each one should be done in a separate
113 # invocation of Lisp so that they don't interfere.
114 echo //running '*.impure-cload.lisp' tests
115 for f in *.impure-cload.lisp; do
117 echo //running $f test
118 $SBCL <<EOF ; tenfour
123 (ignore-errors (delete-file (compile-file-pathname "$f"))))
124 (sb-ext:quit :unix-status 104))
129 # (*.before-xc.lisp and *.after-xc.lisp files aren't handled in this
130 # script at all. They're tests intended to run in the cross-compiler,
131 # so that some functionality can be tested even when cold init doesn't
134 echo '//apparent success (reached end of run-tests.sh normally)'