diff options
| author | Eric Sunshine <sunshine@sunshineco.com> | 2022-09-01 00:29:47 +0000 |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2022-09-01 10:07:40 -0700 |
| commit | aabc3258a1da5f06e0b2492f450d4b8e7e8137e5 (patch) | |
| tree | ab283dec966538e1050a0da387b02fa69d68492d /t/chainlint/nested-loop-detect-failure.test | |
| parent | t/Makefile: apply chainlint.pl to existing self-tests (diff) | |
| download | git-aabc3258a1da5f06e0b2492f450d4b8e7e8137e5.tar.gz git-aabc3258a1da5f06e0b2492f450d4b8e7e8137e5.zip | |
chainlint.pl: don't require `&` background command to end with `&&`
The exit status of the `&` asynchronous operator which starts a command
in the background is unconditionally zero, and the few places in the
test scripts which launch commands asynchronously are not interested in
the exit status of the `&` operator (though they often capture the
background command's PID). As such, there is little value in complaining
about broken &&-chain for a command launched in the background, and
doing so would only make busy-work for test authors. Therefore, take
this special case into account when checking for &&-chain breakage.
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