apenwarr-redo/t/950-curse/all.do

rm -f *.n[012] countall

. ./check-1.sh
redo-ifchange 1.n0 2.n0 3.n0
DEPS=$(./seq 10 | sed 's/$/.n1/')
redo-ifchange $DEPS
. ../skip-if-minimal-do.sh
. ./check-2.sh
t/stress: add a test that usually triggers a bug using 950-curse. It looks like we're updating the stamp for t/countall while another task is replacing the file, which suggests a race condition in our state management database. 2018-10-12 05:48:56 -04:00			`rm -f *.n[012] countall`
t/all.do: use redo instead of redo-ifchange. I'm not quite sure what I was thinking, using redo-ifchange there, but the result was that some tests wouldn't run if you run 'redo test' repeatedly, even after modifying redo itself. Also tweaked t/950-curse so that it always runs, not just the first time. 2018-10-12 04:17:19 -04:00
t/curse: add a Makefile so we can compare speed when using GNU make. redo: 5.4s redo -j4: 3.0s make: 2.3s make -j4: 1.4s make SHELL=/bin/dash: 1.2s make SHELL=/bin/dash -j4: 0.83s We have some distance to go yet. Of course, redo is still written in python, not C, so it's very expensive, and the on-disk dependency store is very inefficient. 2010-11-21 00:31:48 -08:00			`. ./check-1.sh`
Add t/curse, a multi-level dependency build that really aggravates redo. ...because it seems my locking isn't very good. It exposes annoying problems involving rebuilding the same files more than once, screwing up stamp files with redo -j, and being unnecessarily slow when checking dependencies. So it's a pretty good test considering how simple it is. Didn't add it to t/all.do yet, because it would fail. 2010-11-19 00:28:16 -08:00			`redo-ifchange 1.n0 2.n0 3.n0`
Fix tests on MacOS. This comes down to the lack of a 'seq' command (what?!) and the fact that BSD "wc -l" returns extra whitespace, while the GNU version doesn't. We should be using numeric comparisons instead of string comparisons, and then it's ok. 2010-12-12 05:38:30 -08:00			`DEPS=$(./seq 10 \| sed 's/$/.n1/')`
Add t/curse, a multi-level dependency build that really aggravates redo. ...because it seems my locking isn't very good. It exposes annoying problems involving rebuilding the same files more than once, screwing up stamp files with redo -j, and being unnecessarily slow when checking dependencies. So it's a pretty good test considering how simple it is. Didn't add it to t/all.do yet, because it would fail. 2010-11-19 00:28:16 -08:00			`redo-ifchange $DEPS`
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`
t/curse: add a Makefile so we can compare speed when using GNU make. redo: 5.4s redo -j4: 3.0s make: 2.3s make -j4: 1.4s make SHELL=/bin/dash: 1.2s make SHELL=/bin/dash -j4: 0.83s We have some distance to go yet. Of course, redo is still written in python, not C, so it's very expensive, and the on-disk dependency store is very inefficient. 2010-11-21 00:31:48 -08:00			`. ./check-2.sh`