apenwarr-redo/t/clean.do

/bin/ls [0-9s][0-9][0-9]*/clean.do |
sed 's/\.do$//' |
xargs redo

rm -f broken shellfile shellfail shelltest.warned shelltest.failed \
	*~ .*~ stress.log flush-cache
rm -rf 'space home dir'
t/clean.do: don't forget to run s??/clean. 2018-11-02 02:20:29 -04:00			`/bin/ls [0-9s][0-9][0-9]*/clean.do \|`
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			`sed 's/\.do$//' \|`
			`xargs redo`

shelltest.od: add more "set -e" tests and add a 'skip' return code. Based on the earlier t/000-set-minus-e bug in minimal/do on some shells, let's add some extra tests that reveal the weirdness on those shells. Unfortunately because they are so popular (including bash and zsh), we can't reject them outright for failing this one. While we're here, add a new return code, "skip", which notes that a test has failed but is not important enough to be considered a warning or failure. Previously we just had these commented out, which is not quite obvious enough. ...and I updated a few comments while reviewing some of the older tests. 2018-12-17 12:35:32 +00:00			`rm -f broken shellfile shellfail shelltest.warned shelltest.failed \`
shelltest.od: we accidentally treated some fails as mere warnings. We were setting a global variable FAIL on failure, but if we failed inside a subshell (which a very small number of tests might do), this setting would be lost. The script output (a series of failed/warning lines) was still valid, but not the return code, so the shell might be selected even if one of these tests failed. To avoid the problem, put the fail/warning state in the filesystem instead, which is shared across subshells. 2018-12-17 12:33:17 +00:00			`~ .~ stress.log flush-cache`
Missing a couple of rules in t/clean.do files. 2018-10-11 02:50:52 -04:00			`rm -rf 'space home dir'`