zsh-workers
 help / color / mirror / code / Atom feed
From: Axel Beckert <abe@deuxchevaux.org>
To: zsh-workers@zsh.org
Subject: Re: Drat, Test/A05 still hanging sometimes
Date: Thu, 9 Oct 2014 09:52:00 +0200	[thread overview]
Message-ID: <20141009075200.GV5405@sym.noone.org> (raw)
In-Reply-To: <20141007150735.264a09fe@pwslap01u.europe.root.pri>

Hi,

On Tue, Oct 07, 2014 at 03:07:35PM +0100, Peter Stephenson wrote:
> On Mon, 06 Oct 2014 13:42:55 -0700
> Bart Schaefer <schaefer@brasslantern.com> wrote:
> > The interesting thing is where it is stuck.

With the 5.0.7 upload, again one of the Debian builds (so far, two
still outstanding) hung for more than 150 minutes, this time in
A01grammar.ztst:

https://buildd.debian.org/status/fetch.php?pkg=zsh&arch=mipsel&ver=5.0.7-1&stamp=1412817576

Relevant lines:

../../Test/A01grammar.ztst: starting.
Running test: Basic pipeline handling
Test successful.
Running test: Exit status of pipeline with builtins (true)
Test successful.
Running test: Exit status of pipeline with builtins (false)
Test successful.
Running test: Executing command that evaluates to empty resets status
Test successful.
Running test: Starting background command resets status
Test successful.
Running test: Sourcing empty file resets status
Test successful.
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.

HTH.

> As this isn't new, and isn't easily tractable at the moment, I'm not
> planning on holding up 5.0.7.

I think that was the right decision. Sorry for not being able to
report sooner this time, but I was quite busy the past few days.

> I suppose it's likely to be another missing queue_signals(), the
> question is where.

(I'd obviously be happy if someone finds that one, but I have even no
idea where to start looking.)

		Kind regards, Axel
-- 
/~\  Plain Text Ribbon Campaign                   | Axel Beckert
\ /  Say No to HTML in E-Mail and News            | abe@deuxchevaux.org  (Mail)
 X   See http://www.nonhtmlmail.org/campaign.html | abe@noone.org (Mail+Jabber)
/ \  I love long mails: http://email.is-not-s.ms/ | http://noone.org/abe/ (Web)


  reply	other threads:[~2014-10-09  7:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-06 20:42 Bart Schaefer
2014-10-07 14:07 ` Peter Stephenson
2014-10-09  7:52   ` Axel Beckert [this message]
2014-10-12 18:47     ` Bart Schaefer
2014-10-13  3:03       ` Axel Beckert
2014-10-13 17:18         ` Bart Schaefer
2014-10-14  9:34           ` Axel Beckert
2014-10-27  0:40             ` Bart Schaefer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20141009075200.GV5405@sym.noone.org \
    --to=abe@deuxchevaux.org \
    --cc=zsh-workers@zsh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).