zsh-workers
 help / color / mirror / code / Atom feed
From: Axel Beckert <abe@deuxchevaux.org>
To: zsh-workers@zsh.org
Subject: Re: zsh 5.0.5-dev-2 / Occassional hangs on Test/A05execution.ztst
Date: Thu, 14 Aug 2014 19:34:30 +0200	[thread overview]
Message-ID: <20140814173428.GL6176@sym.noone.org> (raw)
In-Reply-To: <20140814163124.GK6176@sym.noone.org>

Hi again,

some more gathered thoughts and experiments around this issue:

On Thu, Aug 14, 2014 at 06:31:25PM +0200, Axel Beckert wrote:
> So far I wasn't able to reproduce the error in a setup where I can
> debug it yet. I've run the testsuite successfully about 70 times each
> for the dynamically linked zsh as well as the statically linked zsh on
> kfreebsd-amd64.

One thing I noticed in the failed build logs: Exactly before
terminating the hanging test suite there is the following message:

Unable to change MONITOR option

Full context:

../../Test/A05execution.ztst: starting.
Unable to change MONITOR option
This test takes 5 seconds to fail...
E: Caught signal ‘Terminated’: terminating immediately
make[1]: *** [test] Terminated
make[2]: *** [check] Terminated
Makefile:264: recipe for target 'test' failed
debian/rules:48: recipe for target 'build-arch' failed
Makefile:188: recipe for target 'check' failed
make: *** [build-arch] Terminated
Build killed with signal TERM after 150 minutes of inactivity

Full log:

https://buildd.debian.org/status/fetch.php?pkg=zsh&arch=kfreebsd-amd64&ver=5.0.5-dev-2-1&stamp=1407936338

Then again this works well despite producing the above message, even many
times in a row:

% ssh localhost "cd `pwd`;./ztst.zsh A05execution.ztst"
A05execution.ztst: starting.
Unable to change MONITOR option
This test takes 5 seconds to fail...
A05execution.ztst: all tests successful.
%

Even inside the kfreebsd-amd64 chroot where I installed the freshly
and sucessfully (locally) built zsh 5.0.5-dev-2 package, I couldn't
reproduce it in a shell not being connected to a terminal.

I also thought, I remember having seen that before on zsh builds on
Debian GNU/Hurd I completely disabled the test-suite there. But at
least https://buildd.debian.org/status/fetch.php?pkg=zsh&arch=hurd-i386&ver=5.0.5-1&stamp=1389022672,
https://buildd.debian.org/status/fetch.php?pkg=zsh&arch=hurd-i386&ver=5.0.4-1&stamp=1387664312
and https://buildd.debian.org/status/fetch.php?pkg=zsh&arch=hurd-i386&ver=5.0.3-1&stamp=1387092681
hung in Test/V08zpty.ztst and had no such message about the MONITOR
option.

So it's probably not (directly) related to not running on a connected
terminal.

(And JFTR: There were no build failures on kfreebsd-amd64 since 2009
with 4.3.10 and later until this week:
https://buildd.debian.org/status/logs.php?pkg=zsh&arch=kfreebsd-amd64
:-)

> I'm now back to trying to reproduce it on that (linux amd64) machine
> were I initially run into it a single time. With some luck, I may be
> able to trigger it and then debug it.

For that I ran the same kind of build where I ran into it locally
once, but modified so that the test suite runs 100 times in a row
instead of only once. No hangs either, though. :-(

		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-08-14 17:34 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-12 20:29 zsh 5.0.5-dev-2 Peter Stephenson
2014-08-12 22:36 ` Axel Beckert
2014-08-13 14:04   ` zsh 5.0.5-dev-2 / Occassional hangs on Test/A05execution.ztst Axel Beckert
2014-08-13 19:08     ` Bart Schaefer
2014-08-14  8:48       ` Axel Beckert
2014-08-14  8:50       ` Peter Stephenson
2014-08-14 16:25         ` Bart Schaefer
2014-08-14 16:31           ` Axel Beckert
2014-08-14 17:34             ` Axel Beckert [this message]
2014-08-15  4:50               ` Bart Schaefer
2014-08-15  9:32                 ` Axel Beckert
2014-08-15 17:33                   ` Bart Schaefer
2014-08-15 19:42                     ` Axel Beckert
2014-08-16 18:12                       ` zsh 5.0.5/6 Peter Stephenson
2014-08-13 17:28   ` zsh 5.0.5-dev-2 Dominic Hopf
2014-08-13 22:34 ` Oliver Kiddle
2014-08-14  8:34   ` Peter Stephenson
2014-08-14  9:32     ` Peter Stephenson
2014-08-14 16:20       ` Bart Schaefer
2014-08-14 19:54         ` Peter Stephenson
2014-08-15  4:44           ` Bart Schaefer
2014-08-15  8:38             ` Peter Stephenson
2014-08-15 11:23             ` Han Pingtian
2014-08-15 17:17               ` Bart Schaefer
2014-08-16  0:35                 ` Han Pingtian
2014-08-17 17:30                   ` Bart Schaefer
2014-08-18  2:56                     ` Han Pingtian
2014-08-18  6:36                       ` Bart Schaefer
2014-08-18 14:02                         ` Han Pingtian
2014-08-23 17:51                     ` Symlink chasing Peter Stephenson

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=20140814173428.GL6176@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).