summaryrefslogtreecommitdiffstats
path: root/Documentation/CodingGuidelines
diff options
context:
space:
mode:
authorJeff King <peff@peff.net>2026-04-10 12:06:08 +0300
committerJunio C Hamano <gitster@pobox.com>2026-04-10 07:58:55 -0700
commit75b7cb5e14f03965cf87a976356bcbdcfb4edbad (patch)
treeae5c7c5486d6da793ca210fc110b374b37a14038 /Documentation/CodingGuidelines
parent495b7d54dc006556548e2fd3ca15c4f533917329 (diff)
downloadgit-75b7cb5e14f03965cf87a976356bcbdcfb4edbad.tar.gz
git-75b7cb5e14f03965cf87a976356bcbdcfb4edbad.zip
t1800: test SIGPIPE with parallel hooks
We recently fixed a bug in commit 2226ffaacd (run_processes_parallel(): fix order of sigpipe handling, 2026-04-08) where a hook that caused us to get SIGPIPE would accidentally trigger the run_processes_parallel() cleanup handler killing the child processes. For a single hook, this meant killing the already-exited hook. This case was triggered by our tests, but was only a problem on some platforms. But if you have multiple hooks running in parallel, this causes a problem everywhere, since one hook failing to read its input would take down all hooks. Now that we have parallel hook support, we can add a test for this case. It should pass already, due to the existing fix. Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Adrian Ratiu <adrian.ratiu@collabora.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/CodingGuidelines')
0 files changed, 0 insertions, 0 deletions