From: "Vin Shelton" <acs@alumni.princeton.edu>
To: zsh-workers@sunsite.dk
Subject: Test hang in Y01
Date: Sat, 10 Jan 2009 10:44:49 -0500 [thread overview]
Message-ID: <20a807210901100744w2f8c2c21h32da38cf2bc461ad@mail.gmail.com> (raw)
Greetings -
With an up-to-date archive, I'm getting a hang in test Y01. Here's
what I found:
; ZTST_verbose=2 make TESTNUM=Y01 check
if test -n "gcc"; then \
cd .. && DESTDIR= \
make MODDIR=`pwd`/Test/Modules install.modules > /dev/null; \
fi
if ZTST_testlist="`for f in /opt/src/zsh-2009-01-09/Test/Y01*.ztst; \
do echo $f; done`" \
ZTST_srcdir="/opt/src/zsh-2009-01-09/Test" \
ZTST_exe=../Src/zsh \
../Src/zsh +Z -f /opt/src/zsh-2009-01-09/Test/runtests.zsh; then \
stat=0; \
else \
stat=1; \
fi; \
rm -rf Modules .zcompdump; \
exit $stat
/opt/src/zsh-2009-01-09/Test/Y01completion.ztst: starting.
ZTST_getsect: read section name: prep
ZTST_getchunk: read code chunk:
if ( zmodload -i zsh/zpty ) >/dev/null 2>&1; then
. $ZTST_srcdir/comptest
mkdir comp.tmp
cd comp.tmp
comptestinit -z $ZTST_testdir/../Src/zsh &&
{
mkdir dir1 &&
mkdir dir2 &&
touch file1 &&
touch file2
}
else
ZTST_unimplemented="the zsh/zpty module is not available"
fi
ZTST_execchunk: status 0
ZTST_getchunk: read code chunk:
ZTST_getsect: read section name: test
ZTST_test: looking for new test
ZTST_test: examining line:
ZTST_test: examining line:
comptest $': \t\t\t\t\t\t\t'
ZTST_getchunk: read code chunk:
comptest $': \t\t\t\t\t\t\t'
ZTST_test: examining line:
>line: {: }{}
ZTST_getredir: read redir for '>':
line: {: }{}
DESCRIPTION:{file}
DI:{dir1}
DI:{dir2}
FI:{file1}
FI:{file2}
line: {: dir1/}{}
line: {: dir2/}{}
line: {: file1}{}
line: {: file2}{}
line: {: dir1/}{}
line: {: dir2/}{}
ZTST_test: examining line:
Running test: directories and files
ZTST_test: expecting status: 0
Input: /tmp/zsh.ztst.in.30417, output: /tmp/zsh.ztst.out.30417, error:
/tmp/zsh.ztst.terr.30417
The err file is empty. The output file contains only:
line: {: }{}
DESCRIPTION:{file}
DI:{dir1}
DI:{dir2}
FI:{file1}
FI:{file2}
line: {: dir1/}{}
line: {: dir2/}{}
line: {: file1}{}
line: {: file2}{}
line: {: dir1/}{}
line: {: dir2/}{}
Let me know if you need any more information.
Regards,
Vin
next reply other threads:[~2009-01-10 15:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-10 15:44 Vin Shelton [this message]
2009-01-10 17:34 ` Bart Schaefer
2009-01-10 18:34 ` Vin Shelton
2009-01-10 21:48 ` Peter Stephenson
[not found] ` <20a807210901101719p58000b77sd0e37bf8b86469a9@mail.gmail.com>
2009-01-11 1:22 ` Vin Shelton
2009-01-11 5:45 ` Geoff Wing
2009-01-11 14:18 ` Peter Stephenson
2009-01-11 17:46 ` Bart Schaefer
2009-01-12 2:25 ` Vin Shelton
2009-01-12 3:19 ` Geoff Wing
2009-01-13 12:00 ` Peter Stephenson
2009-01-13 12:23 ` Peter Stephenson
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=20a807210901100744w2f8c2c21h32da38cf2bc461ad@mail.gmail.com \
--to=acs@alumni.princeton.edu \
--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).