From: Bart Schaefer <schaefer@brasslantern.com>
To: DervishD <raul@pleyades.net>
Cc: Zsh Workers <zsh-workers@sunsite.dk>
Subject: Re: Test E01 and Y01 fails in my zsh 4.0.9
Date: Wed, 7 Jan 2004 21:09:45 +0000 [thread overview]
Message-ID: <1040107210945.ZM10947@candle.brasslantern.com> (raw)
In-Reply-To: <20040107185618.GE13633@DervishD>
On Jan 7, 7:56pm, DervishD wrote:
}
} > } When doing 'make check', the E01options test fails when testing
} > } the option 'BSD_ECHO'.
} > On what operating system are you testing?
}
} Sorry, I forgot to tell: Linux, a DIY box running 2.4.21 kernel
} with glibc 2.2.4
Hrm. I can't think of any reason, offhand, for that failure. The output
you quoted would indicate that it's behaving as if BSD_ECHO is always on.
} Maybe PTY handling is the problem, but if I run the test as you
} say, the test is indeed more verbose but hangs anyway :( It stops at:
}
} comptestinit -z $ZTST_testdir/../Src/zsh &&
[...]
} Don't know why 'comptestinit' stops there :??
It could be a problem with globbing to initialize the fpath, but it's
far more likely that the zpty module is hanging it.
} BTW, I have /dev/ptmx AND /dev/ptyp? so the test shouldn't fail
} even if zsh thinks I don't have the PTY multiplexer :?
If it were a problem with _finding_ the PTY, you wouldn't even get as
far as hanging. I'd suspect a problem with actually reading or writing
the PTY.
As what user are you testing?
next prev parent reply other threads:[~2004-01-07 21:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-07 12:11 DervishD
2004-01-07 16:02 ` Bart Schaefer
2004-01-07 18:56 ` DervishD
2004-01-07 21:09 ` Bart Schaefer [this message]
2004-01-07 21:26 ` DervishD
2004-01-07 22:30 ` Bart Schaefer
2004-01-07 23:46 ` DervishD
2004-01-09 11:54 ` DervishD
2004-01-31 22:06 ` zpty and sutff Alexey Tourbin
2004-01-31 23:49 ` DervishD
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=1040107210945.ZM10947@candle.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=raul@pleyades.net \
--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).