forks/apenwarr-redo
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
apenwarr-redo/t/122-defaults-parent
History
Avery Pennarun e5a27f04e8 If redo searched all the way up to /default.do, it would run ./default.do instead. 
This only happened if the containing project was buggy, ie. you tried
to build a target that has no .do file available anywhere. However, it
resulted in a confusing outcome for that case, where we'd run the wrong
default.do file with the wrong parameters.

Extended an existing test to catch this mistake.
2019-03-02 04:05:36 -05:00
..
inner Certain redo post-build failures would still mark a target as built. 2019-03-02 04:05:36 -05:00
inner2 If redo searched all the way up to /default.do, it would run ./default.do instead. 2019-03-02 04:05:36 -05:00
x Certain redo post-build failures would still mark a target as built. 2019-03-02 04:05:36 -05:00
.gitignore Certain redo post-build failures would still mark a target as built. 2019-03-02 04:05:36 -05:00
all.do If redo searched all the way up to /default.do, it would run ./default.do instead. 2019-03-02 04:05:36 -05:00
clean.do Certain redo post-build failures would still mark a target as built. 2019-03-02 04:05:36 -05:00