ec72beb343
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.
28 lines
943 B
Text
28 lines
943 B
Text
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
|