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.
This commit is contained in:
parent
90989d1ffb
commit
e5a27f04e8
4 changed files with 18 additions and 4 deletions
2
t/122-defaults-parent/inner2/default.do
Normal file
2
t/122-defaults-parent/inner2/default.do
Normal file
|
|
@ -0,0 +1,2 @@
|
|||
echo "inner/default.do: PWD=$PWD '$1' '$2' '$3'" >&2
|
||||
# output file is left empty
|
||||
Loading…
Add table
Add a link
Reference in a new issue