apenwarr-redo/t/200-shell/shelltest.do

set +e
export SHELLTEST_QUIET=1
cd ..
( . ./shelltest.od )
RV=$?
case $RV in
	40) exit 0 ;;
	42) exit 0 ;;
	*) exit 1 ;;
esac
Automatically select a good shell instead of relying on /bin/sh. This includes a fairly detailed test of various known shell bugs from the autoconf docs. The idea here is that if redo works on your system, you should be able to rely on a good shell to run your .do files; you shouldn't have to work around zillions of bugs like autoconf does. 2010-12-21 04:19:50 -08:00			`set +e`
t/shelltest.od: quiet some error messages that get printed during testing. If the error message only triggered a shelltest warning instead of a failure, then they're harmless, so we might as well silence them when running 'redo test' (which runs t/shelltest.do, which enables SHELLTEST_QUIET). We still want to print them when actually testing out shelltest.od, though, to help with debugging the script. 2011-05-08 01:23:32 -04:00			`export SHELLTEST_QUIET=1`
t/*: rearrange tests into numbered directories. It was getting way too ad-hoc in there. Let's reorganize the tests so that there's a good, obvious, suggested sequence to run them in. 2012-02-08 00:33:00 -05:00			`cd ..`
Automatically select a good shell instead of relying on /bin/sh. This includes a fairly detailed test of various known shell bugs from the autoconf docs. The idea here is that if redo works on your system, you should be able to rely on a good shell to run your .do files; you shouldn't have to work around zillions of bugs like autoconf does. 2010-12-21 04:19:50 -08:00			`( . ./shelltest.od )`
			`RV=$?`
			`case $RV in`
shelltest: use a more magical magic number for success. There may be some odd situation where a shell returns 0 despite not executing the script correctly; now 0 is an error condition. 2011-04-17 23:39:53 -04:00			`40) exit 0 ;;`
Automatically select a good shell instead of relying on /bin/sh. This includes a fairly detailed test of various known shell bugs from the autoconf docs. The idea here is that if redo works on your system, you should be able to rely on a good shell to run your .do files; you shouldn't have to work around zillions of bugs like autoconf does. 2010-12-21 04:19:50 -08:00			`42) exit 0 ;;`
			`*) exit 1 ;;`
			`esac`