From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>,
"ZSH Workers Mailing List" <zsh-workers@sunsite.dk>
Subject: Re: Weird test failures under Cygwin
Date: Thu, 10 May 2001 17:53:45 +0000 [thread overview]
Message-ID: <1010510175345.ZM23904@candle.brasslantern.com> (raw)
In-Reply-To: <001801c0d969$f0956550$21c9ca95@mow.siemens.ru>
On May 10, 7:57pm, Andrej Borsenkow wrote:
}
} May be, somebody has an idea.
When run all together, the tests re-use the same zpty name, though not
the same pty instance. I wonder if there's a lurking bug with pty re-use,
either in zpty or in cygwin.
It would appear that some of the output read from zpty is simply getting
lost. I was just able to get an error very similar to this one:
} *** /tmp/zsh.ztst.out.2132 Thu May 10 19:51:12 2001
} --- /tmp/zsh.ztst.tout.2132 Thu May 10 19:51:12 2001
} ***************
} *** 1,3 ****
} line: {tst }{}
} - COMPADD:{_tst:compadd: unknown match specification character `z'}
} - INSERT_POSITIONS:{}
} --- 1 ----
I did it by inserting into the "comptesteval" call in "comptestinit" the
argument "exec 2>>| $ZTST_testdir/comptest.log" (trying to examine exactly
how zsh re-uses the pty). The error I got was:
*** /tmp/zsh.ztst.out.23791 Thu May 10 10:46:42 2001
--- /tmp/zsh.ztst.tout.23791 Thu May 10 10:46:43 2001
***************
*** 1,3 ****
line: {tst }{}
! COMPADD:{_tst:compadd: unknown match specification character `z'}
INSERT_POSITIONS:{}
--- 1,3 ----
line: {tst }{}
! COMPADD:{}
INSERT_POSITIONS:{}
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
prev parent reply other threads:[~2001-05-10 17:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-10 15:57 Andrej Borsenkow
2001-05-10 17:20 ` Bart Schaefer
2001-05-10 17:38 ` Andrej Borsenkow
2001-05-11 8:15 ` Bart Schaefer
2001-05-10 17:53 ` Bart Schaefer [this message]
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=1010510175345.ZM23904@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=Andrej.Borsenkow@mow.siemens.ru \
--cc=zsh-workers@sunsite.dk \
/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).