mirror of
git://git.code.sf.net/p/sbcl/sbcl
synced 2026-09-10 07:26:40 -04:00
2a0f851524
MERGE-PATHNAMES to get an absolute pathname. (Using TRUENAME would be wrong,
since then we would delete files pointed to by symbolic links, and not the
symbolic links themselves -- a nasty regression that would be!)
Also remove the "for error checking" TRUENAME call from there: unlink will
give us an errno that tells what we need to know -- and lo! there is one
race condition less in the system.
Previously using relative pathnames it was possible to accidentally delete
the wrong file.
Fixes lp#882877.
NB: currently DELETE-DIRECTORY and RENAME-FILE use TRUENAME with just the
aforementioned unfortunate consequence, but I'm hesitant to change them
during the freeze -- so dealing with this issue in them will have to
wait a bit.
135 lines
4.1 KiB
Bash
135 lines
4.1 KiB
Bash
# To be sourced by shell scripts in the test suite.
|
|
|
|
# This software is part of the SBCL system. See the README file for
|
|
# more information.
|
|
#
|
|
# 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.
|
|
|
|
# Before sbcl-1.0.13 or so, we set up some environment variables to
|
|
# the absolute (POSIX) pathname naming the SBCL runtime, core, and
|
|
# home; but this runs afoul of the Bourne shell's repeated
|
|
# tokenization of its inputs, so now we use some shell functions.
|
|
. ../sbcl-pwd.sh
|
|
sbcl_pwd
|
|
|
|
# Make the shell bomb out whenever an unset shell variable is used.
|
|
# Note that scripts may toggle this if necessary.
|
|
set -u
|
|
|
|
# Initialize variables.
|
|
set -a # export all variables at assignment-time.
|
|
# Note: any script that uses the variables that name files should
|
|
# quote them (with double quotes), to contend with whitespace.
|
|
SBCL_HOME="$SBCL_PWD/../contrib"
|
|
SBCL_CORE="$SBCL_PWD/../output/sbcl.core"
|
|
SBCL_RUNTIME="$SBCL_PWD/../src/runtime/sbcl"
|
|
SBCL_ARGS="--noinform --no-sysinit --no-userinit --noprint --disable-debugger"
|
|
|
|
# Scripts that use these variables should quote them.
|
|
TEST_BASENAME="`basename $0`"
|
|
TEST_FILESTEM="`basename "${TEST_BASENAME}" | sed 's/\.sh$//'`"
|
|
TEST_FILESTEM="`echo "${TEST_FILESTEM}" | sed 's/\./-/g'`"
|
|
TEST_DIRECTORY="$SBCL_PWD/$TEST_FILESTEM-$$"
|
|
|
|
# "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.
|
|
# (Of course, zero is the usual success value, but we don't want to
|
|
# use that because SBCL returns that by default, so we might think
|
|
# we passed a test when in fact some error caused us to exit SBCL
|
|
# in a weird unexpected way. In contrast, 104 is unlikely to be
|
|
# returned unless we exit through the intended explicit "test
|
|
# successful" path.
|
|
EXIT_TEST_WIN=104
|
|
# Shell scripts in this test suite also return 104, so we need a
|
|
# convention for distinguishing successful execution of SBCL in one of
|
|
# our scripts.
|
|
EXIT_LISP_WIN=52
|
|
# Any test that exits with status 1 is an explicit failure.
|
|
EXIT_LOSE=1
|
|
|
|
LANG=C
|
|
LC_ALL=C
|
|
set +a
|
|
|
|
run_sbcl () (
|
|
set -u
|
|
if [ $# -gt 0 ]; then
|
|
"$SBCL_RUNTIME" --core "$SBCL_CORE" $SBCL_ARGS "$@"
|
|
else
|
|
"$SBCL_RUNTIME" --core "$SBCL_CORE" $SBCL_ARGS
|
|
fi
|
|
)
|
|
|
|
run_sbcl_with_core () (
|
|
set -u
|
|
core="$1"
|
|
shift
|
|
if [ $# -gt 0 ]; then
|
|
"$SBCL_RUNTIME" --core "$core" "$@"
|
|
else
|
|
"$SBCL_RUNTIME" --core "$core" $SBCL_ARGS
|
|
fi
|
|
)
|
|
|
|
# Most tests that run an SBCL have to check whether the child's exit
|
|
# status. Our convention is that SBCL exits with status
|
|
# $EXIT_LISP_WIN to indicate a successful run; but some tests can't do
|
|
# this (e.g., ones that end in S-L-A-D), or need to indicate some
|
|
# other ways of succeeding. So this routine takes a test name, the
|
|
# exit status of the child, and then an arbitrary number extra
|
|
# arguments that will be treated as status-code/message pairs for
|
|
# unusual successful ways for the inferior SBCL to exit. If the exit
|
|
# code of the SBCL isn't found in the status-codes, the calling script
|
|
# will exit with a failure code.
|
|
check_status_maybe_lose () {
|
|
testname=$1
|
|
status=$2
|
|
lose=1
|
|
if [ $status = $EXIT_LISP_WIN ]; then
|
|
echo "test $testname ok"
|
|
lose=0
|
|
else
|
|
shift; shift;
|
|
while [ $# -gt 0 ]; do
|
|
if [ $status = $1 ]; then
|
|
shift;
|
|
echo "test $testname ok $1"
|
|
lose=0
|
|
break
|
|
fi
|
|
shift; shift
|
|
done
|
|
fi
|
|
if [ $lose = 1 ]; then
|
|
echo "test $testname failed: $status"
|
|
exit $EXIT_LOSE
|
|
fi
|
|
unset lose
|
|
unset status
|
|
unset testname
|
|
}
|
|
|
|
# Not every test needs to touch the file system, but enough do to have
|
|
# them consistently do so in subdirectories. Note that such tests
|
|
# should not change their exit action, or do so only very carefully.
|
|
use_test_subdirectory () {
|
|
if test -d "$TEST_DIRECTORY"
|
|
then
|
|
cleanup_test_subdirectory
|
|
fi
|
|
mkdir "$TEST_DIRECTORY"
|
|
cd "$TEST_DIRECTORY"
|
|
trap "cleanup_test_subdirectory" EXIT
|
|
}
|
|
|
|
cleanup_test_subdirectory () {
|
|
cd "$SBCL_PWD"
|
|
( set -f; rm -r "$TEST_DIRECTORY" )
|
|
}
|