apenwarr-redo/t/201-fail/all.do

rm -f this-doesnt-exist
! redo this-doesnt-exist >/dev/null 2>&1 || exit 32  # expected to fail
! redo-ifchange this-doesnt-exist >/dev/null 2>&1 || exit 33  # expected to fail
redo-ifcreate this-doesnt-exist >/dev/null 2>&1 || exit 34  # expected to pass


rm -f fail
! redo-ifchange fail >/dev/null 2>&1 || exit 44  # expected to fail

touch fail
../flush-cache
# since we created this file by hand, fail.do won't run, so it won't fail.
redo-ifchange fail >/dev/null 2>&1 || exit 55  # expected to pass

# Make sure we don't leave this lying around for future runs, or redo
# might mark it as "manually modified" (since we did!)
rm -f fail

rm -f maybe-fail
: >want-fail
! redo-ifchange maybe-fail >/dev/null 2>&1 || exit 66
rm -f want-fail
../flush-cache
redo-ifchange maybe-fail || exit 67  # failed last time, must retry
: >want-fail
../flush-cache
redo-ifchange maybe-fail || exit 68  # passed last time, no dep, no redo
rm -f want-fail
t/201-fail: add a simple test for non-existent source files. (This actually went uncaught in my redo rewrite. Oops.) 2012-02-08 22:47:34 -05:00			`rm -f this-doesnt-exist`
Avoid bashism >&file The >& form is only for file descriptors, passing a file name there is a bash extension. $ /bin/dash -c 'echo foo >&/dev/null' /bin/dash: 1: Syntax error: Bad fd number 2015-08-27 06:57:27 -07:00			`! redo this-doesnt-exist >/dev/null 2>&1 \|\| exit 32 # expected to fail`
			`! redo-ifchange this-doesnt-exist >/dev/null 2>&1 \|\| exit 33 # expected to fail`
			`redo-ifcreate this-doesnt-exist >/dev/null 2>&1 \|\| exit 34 # expected to pass`
t/201-fail: add a simple test for non-existent source files. (This actually went uncaught in my redo rewrite. Oops.) 2012-02-08 22:47:34 -05:00

Test for previous override fix. 2011-03-30 23:29:20 -04:00			`rm -f fail`
Avoid bashism >&file The >& form is only for file descriptors, passing a file name there is a bash extension. $ /bin/dash -c 'echo foo >&/dev/null' /bin/dash: 1: Syntax error: Bad fd number 2015-08-27 06:57:27 -07:00			`! redo-ifchange fail >/dev/null 2>&1 \|\| exit 44 # expected to fail`
t/201-fail: add a simple test for non-existent source files. (This actually went uncaught in my redo rewrite. Oops.) 2012-02-08 22:47:34 -05:00
Test for previous override fix. 2011-03-30 23:29:20 -04:00			`touch fail`
			`../flush-cache`
Use os.lstat() instead of os.stat(). I think this aligns better with how redo works. Otherwise, if a.do creates a as a symlink, then changes to the symlink's target will change a's stat/stamp information without re-running a.do, which looks to redo like you modified a by hand, which causes it to stop running a.do altogether. With this change, modifications to a's target are okay, but they don't trigger any redo dependency changes. If you want that, then a.do should redo-ifchange on its symlink target explicitly. 2018-10-06 00:14:02 -04:00			`# since we created this file by hand, fail.do won't run, so it won't fail.`
Avoid bashism >&file The >& form is only for file descriptors, passing a file name there is a bash extension. $ /bin/dash -c 'echo foo >&/dev/null' /bin/dash: 1: Syntax error: Bad fd number 2015-08-27 06:57:27 -07:00			`redo-ifchange fail >/dev/null 2>&1 \|\| exit 55 # expected to pass`
t/*: some cleanups so switching between redo and minimal/do works. Because the two programs use separate state databases, it helps if we clean up some temp files between runs. Otherwise they might think you created some targets "by hand" and refuse to rebuild them. 2018-10-12 04:18:04 -04:00
			`# Make sure we don't leave this lying around for future runs, or redo`
			`# might mark it as "manually modified" (since we did!)`
			`rm -f fail`
minimal/do: don't create a .did file until after a file is actually built. With the new "continue" feature on by default, it turned out that ctrl-c during a build, or a .do file returning an error, would mark a target as "built" even though it hadn't been. This would prevent retrying it when you started minimal/do again. Use a temp file instead. It's a little tricky: to prevent accidental recursion, we want to create a file before building, but clean up that file when starting the next session. And we rename that file to the actual .did file after building successfully. 2018-11-02 03:48:25 -04:00
			`rm -f maybe-fail`
			`: >want-fail`
			`! redo-ifchange maybe-fail >/dev/null 2>&1 \|\| exit 66`
			`rm -f want-fail`
			`../flush-cache`
			`redo-ifchange maybe-fail \|\| exit 67 # failed last time, must retry`
			`: >want-fail`
			`../flush-cache`
			`redo-ifchange maybe-fail \|\| exit 68 # passed last time, no dep, no redo`
			`rm -f want-fail`