summaryrefslogtreecommitdiff
path: root/t/chainlint/complex-if-in-cuddled-loop.expect
diff options
context:
space:
mode:
authorLibravatar Eric Sunshine <sunshine@sunshineco.com>2021-12-13 01:30:48 -0500
committerLibravatar Junio C Hamano <gitster@pobox.com>2021-12-13 14:15:28 -0800
commit0cca54c706128338ee79efb55e9c0ddb6be723dc (patch)
tree7ecf220ec1ceac2d494fcc5eda710c1703cc9ba0 /t/chainlint/complex-if-in-cuddled-loop.expect
parentt/chainlint/*.test: generalize self-test commentary (diff)
downloadtgif-0cca54c706128338ee79efb55e9c0ddb6be723dc.tar.xz
t/chainlint/one-liner: avoid overly intimate chainlint.sed knowledge
The purpose of chainlint.sed is to detect &&-chain breakage only within subshells (one level deep); it doesn't bother checking for top-level &&-chain breakage since the &&-chain checker built into t/test-lib.sh should detect broken &&-chains outside of subshells by making them magically exit with code 117. Unfortunately, one of the chainlint.sed self-tests has overly intimate knowledge of this particular division of responsibilities and only cares about what chainlint.sed itself will produce, while ignoring the fact that a more all-encompassing linter would complain about a broken &&-chain outside the subshell. This makes it difficult to re-use the test with a more capable chainlint implementation should one ever be developed. Therefore, adjust the test and its "expected" output to avoid being specific to the tunnel-vision of this one implementation. Signed-off-by: Eric Sunshine <sunshine@sunshineco.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/chainlint/complex-if-in-cuddled-loop.expect')
0 files changed, 0 insertions, 0 deletions