summaryrefslogtreecommitdiffstats
path: root/t/t4013/diff.format-patch_--inline_--stdout_initial..master^
diff options
context:
space:
mode:
authorPatrick Steinhardt <ps@pks.im>2026-04-21 09:34:16 +0200
committerJunio C Hamano <gitster@pobox.com>2026-04-22 15:53:35 -0700
commitf43d01ab90be2711927c8d265b3fb21d2213d2ab (patch)
treecd0249763b47292b4ba5ceada2883522c133febc /t/t4013/diff.format-patch_--inline_--stdout_initial..master^
parent990fd368ac7fcb56f69a27ba341cac10f04e285b (diff)
downloadgit-f43d01ab90be2711927c8d265b3fb21d2213d2ab.tar.gz
git-f43d01ab90be2711927c8d265b3fb21d2213d2ab.zip
t: prepare `stop_git_daemon ()` for `set -e`
We have a couple of calls to `stop_git_daemon ()` outside of specific test cases that will kill a backgrounded git-daemon(1) process and expect the process with a specific error code. While these function calls do end up killing git-daemon(1), the error handling we have in those contexts is basically ineffective. So while we expect the process to exit with a specific error code, we will just continue with any error in case it doesn't. This will change once we enable `set -e` in a subsequent commit. There's two issues though that will make this _always_ fail: - Our call to `wait` is expected to fail, but because it's not part of a condition it will cause us to bail out immediately with `set -e`. - We try to kill git-daemon(1) a second time via the pidfile. We can generally expect that this is the same PID though as we had in the "GIT_DAEMON_PID" environment variable, and thus it's more likely than not that we have already killed it, and the call to kill will fail. Prepare for this change by handling the failure of `wait` with `||` and by silencing failures of the second call to `kill`. Signed-off-by: Patrick Steinhardt <ps@pks.im> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t4013/diff.format-patch_--inline_--stdout_initial..master^')
0 files changed, 0 insertions, 0 deletions