git/t/chainlint/chain-break-background.expect at 07011e14803db7f38530efa73324ab7b385328b8 - development/git - HydraGit

development/git

mirror of https://github.com/git/git synced 2024-10-31 00:45:12 +00:00

Eric Sunshine aabc3258a1 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>

2022-09-01 10:07:40 -07:00

9 lines

295 B

Text

Raw Blame History

 JGIT_DAEMON_PID= &&
 git init --bare empty.git &&
 > empty.git/git-daemon-export-ok &&
 mkfifo jgit_daemon_output &&
 {
 	jgit daemon --port="$JGIT_DAEMON_PORT" . > jgit_daemon_output &
 	JGIT_DAEMON_PID=$!
 } &&
 test_expect_code 2 git ls-remote --exit-code git://localhost:$JGIT_DAEMON_PORT/empty.git