From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12728 invoked by alias); 6 Oct 2014 20:43:08 -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: 33374 Received: (qmail 24201 invoked from network); 6 Oct 2014 20:42:57 -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.8 required=5.0 tests=BAYES_00,FROM_12LTRDOM, RCVD_IN_DNSWL_NONE,T_MANY_HDRS_LCASE autolearn=no version=3.3.2 From: Bart Schaefer Message-id: <141006134255.ZM22326@torch.brasslantern.com> Date: Mon, 06 Oct 2014 13:42:55 -0700 X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-workers@zsh.org Subject: Drat, Test/A05 still hanging sometimes MIME-version: 1.0 Content-type: text/plain; charset=us-ascii 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.