From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7943 invoked by alias); 12 Oct 2014 18:47:35 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 33449 Received: (qmail 24373 invoked from network); 12 Oct 2014 18:47:34 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 From: Bart Schaefer Message-id: <141012114739.ZM23982@torch.brasslantern.com> Date: Sun, 12 Oct 2014 11:47:39 -0700 In-reply-to: <20141009075200.GV5405@sym.noone.org> Comments: In reply to Axel Beckert "Re: Drat, Test/A05 still hanging sometimes" (Oct 9, 9:52am) References: <141006134255.ZM22326@torch.brasslantern.com> <20141007150735.264a09fe@pwslap01u.europe.root.pri> <20141009075200.GV5405@sym.noone.org> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-workers@zsh.org Subject: Re: Drat, Test/A05 still hanging sometimes MIME-version: 1.0 Content-type: text/plain; charset=us-ascii On Oct 9, 9:52am, Axel Beckert wrote: } } Running test: Basic coprocess handling } make: *** [build-arch] Terminated } make[1]: *** [test] Terminated } make[2]: *** [check] Terminated } debian/rules:54: recipe for target 'build-arch' failed } Makefile:265: recipe for target 'test' failed } Makefile:189: recipe for target 'check' failed } Build killed with signal TERM after 150 minutes of inactivity } } I assume it's too far away (in terms of output size) from A05 to have } (not) buffer flushing causing the output being incomplete. It is indeed too far away but: The test in A05 that gets stuck also uses a coprocess, so the likely place to look is a race condition in the SIGCHLD reaping of coprocesses. Tests in each of A01, A04, and A05 use "coproc". How does this match up with the hung builds you have encountered?