summaryrefslogtreecommitdiff
path: root/t/chainlint/nested-loop-detect-failure.test
diff options
context:
space:
mode:
authorEric Sunshine <sunshine@sunshineco.com>2022-08-22 18:26:42 +0000
committerJunio C Hamano <gitster@pobox.com>2022-08-22 12:53:02 -0700
commit0e66bc1b215b1dd2b0f05c5777eb8ee2ae4e9523 (patch)
tree12e41d0779a59a42f52889fb94e5607f8a273363 /t/chainlint/nested-loop-detect-failure.test
parent625ff5c3201186cedb856678907a3f4bd88406a6 (diff)
t: detect and signal failure within loop
Failures within `for` and `while` loops can go unnoticed if not detected and signaled manually since the loop itself does not abort when a contained command fails, nor will a failure necessarily be detected when the loop finishes since the loop returns the exit code of the last command it ran on the final iteration, which may not be the command which failed. Therefore, detect and signal failures manually within loops using the idiom `|| return 1` (or `|| exit 1` within subshells). Signed-off-by: Eric Sunshine <sunshine@sunshineco.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/chainlint/nested-loop-detect-failure.test')
0 files changed, 0 insertions, 0 deletions