apenwarr-redo/t/alwaystest.do

rm -f always1 always1.log

redo always1
[ "$(wc -l <always1.log)" -eq 1 ] || exit 11

# This shouldn't rebuild, but because other people might be running flush-cache.sh
# in parallel with us, we can't be 100% sure it won't.  So don't test it.
#redo-ifchange always1
#[ "$(wc -l <always1.log)" -eq 1 ] || exit 21

./flush-cache.sh
redo-ifchange always1
. ./skip-if-minimal-do.sh
[ "$(wc -l <always1.log)" -eq 2 ] || exit 31
Add a redo-always command: it adds an "always dirty" dependency to your target. This is mostly useless except when combined with redo-stamp... I think. 2010-12-11 07:02:45 -08:00			`rm -f always1 always1.log`

			`redo always1`
			`[ "$(wc -l <always1.log)" -eq 1 ] \|\| exit 11`

			`# This shouldn't rebuild, but because other people might be running flush-cache.sh`
			`# in parallel with us, we can't be 100% sure it won't. So don't test it.`
			`#redo-ifchange always1`
			`#[ "$(wc -l <always1.log)" -eq 1 ] \|\| exit 21`

			`./flush-cache.sh`
			`redo-ifchange always1`
Disable the tests that don't work with minimal/do. ...only when running under minimal/do, of course. The tests in question mostly fail because they're testing particular dependency-related behaviour, and minimal/do doesn't support dependencies, so naturally it doesn't work. 2010-12-11 20:54:46 -08:00			`. ./skip-if-minimal-do.sh`
Add a redo-always command: it adds an "always dirty" dependency to your target. This is mostly useless except when combined with redo-stamp... I think. 2010-12-11 07:02:45 -08:00			`[ "$(wc -l <always1.log)" -eq 2 ] \|\| exit 31`