zsh-workers
 help / color / mirror / code / Atom feed
From: Axel Beckert <abe@debian.org>
To: zsh-workers@zsh.org
Cc: Debian Zsh Maintainers <pkg-zsh-devel@lists.alioth.debian.org>
Subject: Re: Strange test suite behaviour since zsh 5.2-dev-1: C02cond.ztst no more reports its finishing
Date: Sun, 31 Jan 2016 22:59:30 +0100	[thread overview]
Message-ID: <20160131215930.GM4726@sym.noone.org> (raw)
In-Reply-To: <160131125145.ZM12147@torch.brasslantern.com>

Hi Bart,

Bart Schaefer wrote:
> On Jan 31,  9:19pm, Axel Beckert wrote:
> } Any ideas what could cause this silent exiting of a .ztst script and
> } why it only appears under certain (yet not 100% clear) conditions?
> 
> Silent exit occurs when the test crashes the test-harness shell.

Yeah, sounds reasonable.

> This is an unfortunate side-effect of the way error output is
> managed by the harness; the only way to detect it is to spot
> coredump files, or find temp files that have never been removed,
> left behind after the "make".
> 
> What circumstances are causing the crash, you'll have to try to run
> down.

I'll try to reproduce it locally again and see what I can find. Thanks
for the hints.

		Regards, Axel
-- 
 ,''`.  |  Axel Beckert <abe@debian.org>, http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-    |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE


  reply	other threads:[~2016-01-31 21:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-31 20:19 Axel Beckert
2016-01-31 20:51 ` Bart Schaefer
2016-01-31 21:59   ` Axel Beckert [this message]
2016-01-31 23:03   ` C02cond.ztst segfaults (was: Re: Strange test suite behaviour since zsh 5.2-dev-1: C02cond.ztst no more reports its finishing) Axel Beckert
2016-01-31 23:12     ` Bart Schaefer
2016-01-31 23:20       ` Axel Beckert
2016-02-01  0:18         ` Axel Beckert

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=20160131215930.GM4726@sym.noone.org \
    --to=abe@debian.org \
    --cc=pkg-zsh-devel@lists.alioth.debian.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).