# 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.
-export SBCL="${1:-`pwd`/../src/runtime/sbcl --core `pwd`/../output/sbcl.core --noinform --sysinit /dev/null --userinit /dev/null --noprint --noprogrammer}"
+SBCL="${1:-`pwd`/../src/runtime/sbcl --core `pwd`/../output/sbcl.core --noinform --sysinit /dev/null --userinit /dev/null --noprint --disable-debugger}"
+export SBCL
echo /running tests on SBCL=\'$SBCL\'
# "Ten four" is the closest numerical slang I can find to "OK", so
echo //running $f test
$SBCL <<EOF ; tenfour
(compile-file "$f")
- (progn (load *) (sb-ext:quit :unix-status 104))
+ (progn
+ (unwind-protect
+ (load *)
+ (ignore-errors (delete-file (compile-file-pathname "$f"))))
+ (sb-ext:quit :unix-status 104))
EOF
fi
done
echo //running $f test
$SBCL <<EOF ; tenfour
(compile-file "$f")
- (progn (load *) (sb-ext:quit :unix-status 104))
+ (progn
+ (unwind-protect
+ (load *)
+ (ignore-errors (delete-file (compile-file-pathname "$f"))))
+ (sb-ext:quit :unix-status 104))
EOF
fi
done
# work.)
echo '//apparent success (reached end of run-tests.sh normally)'
+date