From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-34087-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 24192 invoked by alias); 3 Jan 2015 19:56:56 -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: 34087
Received: (qmail 1380 invoked from network); 3 Jan 2015 19:56:43 -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-CMAE-Score: 0
X-CMAE-Analysis: v=2.1 cv=Ko/6AtSI c=1 sm=1 tr=0	a=FT8er97JFeGWzr5TCOCO5w==:117
 a=kj9zAlcOel0A:10 a=q2GGsy2AAAAA:8	a=oR5dmqMzAAAA:8 a=-9mUelKeXuEA:10
 a=YNv0rlydsVwA:10	a=8FVnu-Aoipl994qiVhUA:9 a=CjuIK1q_8ugA:10
From: Bart Schaefer <schaefer@brasslantern.com>
Message-id: <150103115648.ZM23062@torch.brasslantern.com>
Date: Sat, 03 Jan 2015 11:56:48 -0800
In-reply-to: <20150103192925.02c5fa4a@ntlworld.com>
Comments: In reply to Peter Stephenson <p.w.stephenson@ntlworld.com>
 "Re: A05execution.ztst fails on Cygwin" (Jan  3,  7:29pm)
References:
 <CAJ1KOAgr5uUo9P1HfYYuDxanuhR8=eK5phdDJOrZzY-_vOLwQg@mail.gmail.com>
	<20150103192925.02c5fa4a@ntlworld.com>
X-Mailer: OpenZMail Classic (0.9.2 24April2005)
To: "Zsh Hackers' List" <zsh-workers@zsh.org>
Subject: Re: A05execution.ztst fails on Cygwin
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii

On Jan 3,  7:29pm, Peter Stephenson wrote:
}
} 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.

It looks like "[6]  - 2456 running    sleep 1000" got mixed into the
output as well.  That's from a completely different test two or three
places earlier in the A05* file:

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

... and indicates that "kill $!" did not succeed in ending the sleep, so
there are much larger issues here than this garbled output.

} I would expect the first problem you reported to be tractable, though.

I have my doubts ...