forks/apenwarr-redo
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
apenwarr-redo/t/640-always/all.do

26 lines
645 B
Text
Raw Normal View History

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 ..
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
redo 640-always/always1
cd 640-always
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
Rename flush-cache.py to flush-cache, and rearrange the code a bit. It was working fine, but the style wasn't exactly the way I like it, because I'm unnecessarily picky. :) Also, removed the file extension since we should probably learn from the fact that it's already been rewritten once from one language to another. Who knows, maybe it will be again someday.
2011-02-23 01:24:48 -08:00
# This shouldn't rebuild, but because other people might be running
# flush-cache in parallel with us, we can't be 100% sure it won't. So don't
# test it.
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
#[ "$(wc -l <always1.log)" -eq 1 ] || exit 21
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
../flush-cache
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
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
. ../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
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
../flush-cache
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 ..
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
./flush-cache
redo-ifchange 640-always/always1
[ "$(wc -l <640-always/always1.log)" -eq 4 ] || exit 51
Reference in a new issue Copy permalink