zsh-workers
 help / color / mirror / code / Atom feed
From: "İsmail Dönmez" <ismail@donmez.ws>
To: Peter Stephenson <p.w.stephenson@ntlworld.com>
Cc: "Zsh Hackers' List" <zsh-workers@zsh.org>
Subject: Re: A05execution.ztst fails on Cygwin
Date: Sat, 3 Jan 2015 21:59:20 +0200	[thread overview]
Message-ID: <CAJ1KOAgzN0Yu3wTVX99ARyjyBJzLXJQxRDOQZEHQ-OTXW69Y9w@mail.gmail.com> (raw)
In-Reply-To: <20150103192925.02c5fa4a@ntlworld.com>

[-- Attachment #1: Type: text/plain, Size: 2110 bytes --]

Hi,

On Sat, Jan 3, 2015 at 9:29 PM, Peter Stephenson <
p.w.stephenson@ntlworld.com> wrote:

> On Sat, 3 Jan 2015 12:54:21 +0200
> İsmail Dönmez <ismail@donmez.ws> wrote:
> > Using latest git;
> >
> > ./A05execution.ztst: starting.
> > This test takes 5 seconds to fail...
> > Pattern match failed:#######
> > <\[<->\] <-> <->
> > >[8] 3212 4644
> > >[6]  - 2456 running    sleep 1000
>
> That's a bit funny.  It appears to be saying the string
> "[8] 3212 4644" doesn't match the pattern '\[<->\] <-> <->'.  Are
> you able to reproduce this from the command line?
>
>   str='[8] 3212 4644'
>   pat='\[<->\] <-> <->'
>   [[ $str = ${~pat} ]] || print Pattern failed to match
>
> 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 you can turn off hask marks when output is verbose.  Does
>
> ZTST_verbose=1 make TESTNUM=A05
>
> work any better?
>
>
This fixes the test for me.


> > While running make check I noticed that V08zpty.ztst was hanging. Turns
> out
> > that second part of the test is hanging. The minimal reproducer is:
> >
> > zmodload zsh/zpty
> > zpty cat cat
> > print a line of text | zpty -w cat
> > var=
> > zpty -r cat var && print -r -- ${var%%$'\r\n'}
> > zpty -d cat # <--- HANGS
> >
> > I am not sure if Cygwin is a supported platform but any help would be
> > appreciated.
>
> We don't have the resources to differentiate betwen "supported" and
> "unsupported," we just have to try to fix problems as they turn up as
> best we can wherever they turn up.  Cygwin gets less love and attention
> than more standard Unix-like platforms.  In the case of zpty you may be
> onto a loser: it's hard enough on most systems and worse here.  I'm
> aware of historical problems with <(...) and >(...) substitutions, too.
>

It might makes sense to fail this test on Cygwin then, so I could run make
check semi-regularly and make sure no regressions would be introduced.

Regards.

  parent reply	other threads:[~2015-01-03 19:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-03 10:54 İsmail Dönmez
2015-01-03 17:21 ` Ray Andrews
2015-01-03 17:45   ` İsmail Dönmez
2015-01-03 18:37     ` Ray Andrews
2015-01-03 19:29 ` Peter Stephenson
2015-01-03 19:51   ` Peter Stephenson
2015-01-03 19:56   ` Bart Schaefer
2015-01-03 19:59   ` İsmail Dönmez [this message]
2015-01-03 23:02     ` Peter Stephenson
2015-01-09  9:13       ` İsmail Dönmez

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=CAJ1KOAgzN0Yu3wTVX99ARyjyBJzLXJQxRDOQZEHQ-OTXW69Y9w@mail.gmail.com \
    --to=ismail@donmez.ws \
    --cc=p.w.stephenson@ntlworld.com \
    --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).