, I saw it
hanging in the second read. strace revealed that we were blocked on
open(out).
The patch below should fix it. I'm still not sure why the choice of
shell matters; it may simply be a timing fluke that bash is more likely
to hit for some reason.
-- 8 --
Subject: [PATCH] t0008: avoid SIGPIPE
Jeff King p...@peff.net writes:
Subject: [PATCH] t0008: avoid SIGPIPE race condition on fifo
To test check-ignore's --stdin feature, we use two fifos to
send and receive data. We carefully keep a descriptor to its
input open so that it does not receive EOF between input
lines. However, we
On Jul 12, 2013, at 6:35 AM, Jeff King p...@peff.net wrote:
Subject: [PATCH] t0008: avoid SIGPIPE race condition on fifo
Was able to complete a prove run with this patch. Many thanks.
~~ Brian
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord
On Fri, Jul 12, 2013 at 09:23:54AM -0700, Junio C Hamano wrote:
In that case, check-ignore gets a SIGPIPE and dies. The
outer shell then tries to open the output fifo but blocks
indefinitely, because there is no writer. We can fix it by
keeping a descriptor open through the whole
4 matches
Mail list logo