From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-34086-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 20948 invoked by alias); 3 Jan 2015 19:52:04 -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: 34086
Received: (qmail 24285 invoked from network); 3 Jan 2015 19:52:01 -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
X-Originating-IP: [86.6.153.127]
X-Spam: 0
X-Authority: v=2.1 cv=AoZg3YNP c=1 sm=1 tr=0 a=39NrsSuza2clQiZR/7fYWQ==:117
 a=39NrsSuza2clQiZR/7fYWQ==:17 a=IkcTkHD0fZMA:10 a=NLZqzBF-AAAA:8
 a=fR9hA1kLAAAA:8 a=N7d74lT5RdsenZl7J1UA:9 a=QEXdDO2ut3YA:10
Date: Sat, 3 Jan 2015 19:51:57 +0000
From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: "Zsh Hackers' List" <zsh-workers@zsh.org>
Subject: Re: A05execution.ztst fails on Cygwin
Message-ID: <20150103195157.7221bd68@ntlworld.com>
In-Reply-To: <20150103192925.02c5fa4a@ntlworld.com>
References: <CAJ1KOAgr5uUo9P1HfYYuDxanuhR8=eK5phdDJOrZzY-_vOLwQg@mail.gmail.com>
	<20150103192925.02c5fa4a@ntlworld.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Sat, 3 Jan 2015 19:29:25 +0000
Peter Stephenson <p.w.stephenson@ntlworld.com> wrote:
> On Sat, 3 Jan 2015 12:54:21 +0200
> =C4=B0smail D=C3=B6nmez <ismail@donmez.ws> wrote:
> > Using latest git;
> >=20
> > ./A05execution.ztst: starting.
> > This test takes 5 seconds to fail...
> > Pattern match failed:#######
> > <\[<->\] <-> <->
> > >[8] 3212 4644
> > >[6]  - 2456 running    sleep 1000
>=20
> That's a bit funny.  It appears to be saying the string
> "[8] 3212 4644" doesn't match the pattern '\[<->\] <-> <->'.

Ah --- just woke up and looked in more detail at the test and your
output as I should have done before.

The test runs "jobs -l" at the end; it expects the job will have
exited.  Indeed it (%8) has, but another job (%6) is still running.
That's presumably what's causing the failure (though the error message
is a bit unhelpful, which is probably my fault).

It's likely to be a job started by this test:

  false
  sleep 1000 &
  print $?
  kill $!
0:Status reset by starting a backgrounded command
>0

So what failed is that "kill $!".  In this case, job control is probably
off, though we do monkey with MONITOR in various tests so that may not
be guaranteed.  $! should be set, and kill should work, regardless of
job control.  In principle there's a good deal less to go wrong here
than stuff involving job control and ptys...

> Actually, looking at it more closesly, the problem may be that somehow
> the ### output that shows the time being taken have got mixed in with
> standard output from the test itself.

I suspect that's just a side effect of Cygwin/Windows terminal handling,
actually.

pws