git/t/chainlint/chain-break-background.test

JGIT_DAEMON_PID= &&
git init --bare empty.git &&
>empty.git/git-daemon-export-ok &&
mkfifo jgit_daemon_output &&
{
# LINT: exit status of "&" is always 0 so &&-chaining immaterial
	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
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 00:29:47 +00:00			`JGIT_DAEMON_PID= &&`
			`git init --bare empty.git &&`
			`>empty.git/git-daemon-export-ok &&`
			`mkfifo jgit_daemon_output &&`
			`{`
			`# LINT: exit status of "&" is always 0 so &&-chaining immaterial`
			`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`