From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-33013-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 11404 invoked by alias); 15 Aug 2014 04:50:38 -0000
Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Workers List <zsh-workers.zsh.org>
List-Post: <mailto:zsh-workers@zsh.org>
List-Help: <mailto:zsh-workers-help@zsh.org>
X-Seq: 33013
Received: (qmail 11611 invoked from network); 15 Aug 2014 04:50:37 -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.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE
	autolearn=ham version=3.3.2
From: Bart Schaefer <schaefer@brasslantern.com>
Message-id: <140814215053.ZM4188@torch.brasslantern.com>
Date: Thu, 14 Aug 2014 21:50:53 -0700
In-reply-to: <20140814173428.GL6176@sym.noone.org>
Comments: In reply to Axel Beckert <abe@deuxchevaux.org>
 "Re: zsh 5.0.5-dev-2 / Occassional hangs on Test/A05execution.ztst" (Aug 14,
 7:34pm)
References: <20140812212920.67dcb116@pws-pc.ntlworld.com>
	<20140812223637.GS6176@sym.noone.org>	<20140813140401.GX6176@sym.noone.org>
	<CAH+w=7bTeANUWtcuw8ZbuN=sfQNPiH2S8pNtSV+FxU3ijCX=PA@mail.gmail.com>
	<20140814095002.1d8949c5@pwslap01u.europe.root.pri>
	<140814092527.ZM18021@torch.brasslantern.com>
	<20140814163124.GK6176@sym.noone.org>	<20140814173428.GL6176@sym.noone.org>
X-Mailer: OpenZMail Classic (0.9.2 24April2005)
To: zsh-workers@zsh.org
Subject: Re: zsh 5.0.5-dev-2 / Occassional hangs on Test/A05execution.ztst
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii

On Aug 14,  7:34pm, Axel Beckert wrote:
} 
} 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

Yes, that's coming from the third-to-last test in the file:

  { setopt MONITOR } 2>/dev/null
  [[ -o MONITOR ]] || print -u $ZTST_fd 'Unable to change MONITOR option'

Where as the "5 seconds" message is from the very last test:

  { unsetopt MONITOR } 2>/dev/null
  coproc { read -Et 5 || kill -INT $$ }
  print -u $ZTST_fd 'This test takes 5 seconds to fail...'

So two tests have succeeded between the "Unable" message and the one
that hangs.  The inability to change MONITOR is a side-effect of no
controlling terminal, so the test warns you.  Actually the warning
could be stronger than that, because the inability to setpt MONITOR
renders the test invalid (it will always succeed, even in the case
we are trying to regress).