apenwarr-redo/t/alwaystest.do

rm -f always1 always1.log

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

# This shouldn't rebuild, but because other people might be running flush-cache.py
# 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.py
redo-ifchange always1
. ./skip-if-minimal-do.sh
[ "$(wc -l <always1.log)" -eq 2 ] || exit 31

./flush-cache.py
redo-ifchange always1
[ "$(wc -l <always1.log)" -eq 3 ] || exit 41

cd ..
./t/flush-cache.py
redo-ifchange t/always1
[ "$(wc -l <t/always1.log)" -eq 4 ] || exit 51
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-always/redo-ifcreate/redo-stamp: work inside chdir(). If someone cd's to another directory and then runs redo-always, we weren't adding to the right target. 2010-12-11 23:00:53 -08:00			`cd ..`
			`redo t/always1`
			`cd t`
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 1 ] \|\| exit 11`

Fix tests when the sqlite3 command line utility isn't installed. We know the user already has to have python, so use its bindings. 2011-02-22 22:47:00 -06:00			`# This shouldn't rebuild, but because other people might be running flush-cache.py`
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			`# 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`

Fix tests when the sqlite3 command line utility isn't installed. We know the user already has to have python, so use its bindings. 2011-02-22 22:47:00 -06:00			`./flush-cache.py`
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			`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`
redo-always/redo-ifcreate/redo-stamp: work inside chdir(). If someone cd's to another directory and then runs redo-always, we weren't adding to the right target. 2010-12-11 23:00:53 -08:00
Fix tests when the sqlite3 command line utility isn't installed. We know the user already has to have python, so use its bindings. 2011-02-22 22:47:00 -06:00			`./flush-cache.py`
redo-always/redo-ifcreate/redo-stamp: work inside chdir(). If someone cd's to another directory and then runs redo-always, we weren't adding to the right target. 2010-12-11 23:00:53 -08:00			`redo-ifchange always1`
			`[ "$(wc -l <always1.log)" -eq 3 ] \|\| exit 41`

			`cd ..`
Fix tests when the sqlite3 command line utility isn't installed. We know the user already has to have python, so use its bindings. 2011-02-22 22:47:00 -06:00			`./t/flush-cache.py`
redo-always/redo-ifcreate/redo-stamp: work inside chdir(). If someone cd's to another directory and then runs redo-always, we weren't adding to the right target. 2010-12-11 23:00:53 -08:00			`redo-ifchange t/always1`
			`[ "$(wc -l <t/always1.log)" -eq 4 ] \|\| exit 51`