From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18454 invoked by alias); 7 Oct 2014 14:07:53 -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: 33376 Received: (qmail 19744 invoked from network); 7 Oct 2014 14:07:41 -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=-5.4 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_HI, SPF_HELO_PASS,URIBL_RHS_DOB autolearn=ham version=3.3.2 X-AuditID: cbfec7f4-b7f156d0000063c7-59-5433f3a8b496 Date: Tue, 07 Oct 2014 15:07:35 +0100 From: Peter Stephenson To: zsh-workers@zsh.org Subject: Re: Drat, Test/A05 still hanging sometimes Message-id: <20141007150735.264a09fe@pwslap01u.europe.root.pri> In-reply-to: <141006134255.ZM22326@torch.brasslantern.com> References: <141006134255.ZM22326@torch.brasslantern.com> Organization: Samsung Cambridge Solution Centre X-Mailer: Claws Mail 3.7.9 (GTK+ 2.22.0; i386-redhat-linux-gnu) MIME-version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFuphluLIzCtJLcpLzFFi42I5/e/4Vd0Vn41DDI4v0bA42PyQyYHRY9XB D0wBjFFcNimpOZllqUX6dglcGU8OL2MteMhWcXzdQ8YGxhWsXYycHBICJhIzu3YzQthiEhfu rWfrYuTiEBJYyihx/+8eFghnOZPExc/fgao4OFgEVCVmnLIBaWATMJSYumk2WLOIgLjE2bXn WUBsYQFjiftXF4LFeQXsJRYf+cEOYnMKWEl8bFwNFhcSsJRYe+oHG4jNL6AvcfXvJyaII+wl Zl45A9UrKPFj8j2wmcwCWhKbtzWxQtjyEpvXvGWewCgwC0nZLCRls5CULWBkXsUomlqaXFCc lJ5rqFecmFtcmpeul5yfu4kREoJfdjAuPmZ1iFGAg1GJh3eDoXGIEGtiWXFl7iFGCQ5mJRHe Ke+BQrwpiZVVqUX58UWlOanFhxiZODilGhi1Jj9WPXBShDfEwrVzuunhtgP//U6cXP73vHv4 ilr11GdM9+Ljjsbv3q1v92aGzbNJZ+LKNFs2LVLINk/6ZbOsuK1kbUMk568d17dbH2qq6Agq Yj1xZeVRiSeJG0qrN0+NWvFl7cZ7Ah4yHI4Oy3ecFZgo+LRHh71bprdP6vhDz+suc1wNK+8q sRRnJBpqMRcVJwIAVO9E/h8CAAA= On Mon, 06 Oct 2014 13:42:55 -0700 Bart Schaefer wrote: > The interesting thing is where it is stuck. > > The "runtests.zsh" thread is blocked on sigsuspend() in the "for file" loop, > waiting for the the $ZTST_exe thread to finish. > > The $ZTST_exe thread is trying to exit -- in my case it is stuck on a mutex > with no zsh code left in the gdb-able call stack backtrace. > > Strangely, though, if I kill that thread, the runtests thread also dies, > and the entire "make" aborts. The "for file" loop is written in a way that > I would have expected runtests to simply continue on to the next pass. > > I'm baffled. As this isn't new, and isn't easily tractable at the moment, I'm not planning on holding up 5.0.7. I suppose it's likely to be another missing queue_signals(), the question is where. pws