From: Paul Ackersviller <pda@sdf.lonestar.org>
To: zsh-workers@sunsite.dk
Subject: Re: D07multibyte.ztst failure on HP-UX 11.11
Date: Fri, 1 May 2009 14:52:53 +0000 [thread overview]
Message-ID: <20090501145253.GA5070@svalbard> (raw)
In-Reply-To: <200904301603.n3UG3x8I022847@news01.csr.com>
Sorry if anyone gets this twice, I sent it yesterday but haven't seen
it show up on the list yet.
On Thu, Apr 30, 2009 at 05:03:59PM +0100, Peter Stephenson wrote:
> Paul Ackersviller wrote:
> > That gets me past that test, then a subsequent one fails.
>
> Urgh. I can't help feeling it might be better if they just fixed the
> system.
Granted, it is and old, if not already-obsolete, system.
> > ./D07multibyte.ztst: starting.
> > locale en_US.UTF-8 failed
> > *** /tmp/zsh.ztst.out.4937 2009-04-30 11:23:24.000000000 -0400
> > --- /tmp/zsh.ztst.tout.4937 2009-04-30 11:23:24.000000000 -0400
> > ***************
> > *** 1,4 ****
> > - OK
> > - OK
> > - OK
> > - OK
> > --- 0 ----
> > Test ./D07multibyte.ztst failed: output differs from expected as shown above
> > for:
> > testfn() { (LC_ALL=C; print $'\u00e9') }
> > repeat 4 testfn 2>&1 | while read line; do
> > if [[ $line = *"character not in range"* ]]; then
> > print OK
> > elif [[ $line = "?" ]]; then
> > print OK
> > else
> > print Failed: no error message and no question mark
> > fi
> > done
> > true
> > Was testing: error handling in Unicode quoting
> > ./D07multibyte.ztst: test failed.
>
> Eh? How did you manage to get *no* output from that test? What does
> testfn do when run on it's own?
Same thing -- it seems the read is either detecting EOF right off,
or else failing silently somehow. I don't do the if at all,
but I see I can get there by using a non-utf8 value of LANG.
next prev parent reply other threads:[~2009-05-01 14:53 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-27 3:17 Paul Ackersviller
2009-04-27 4:42 ` Andrey Borzenkov
2009-04-27 19:26 ` Paul Ackersviller
2009-04-28 8:48 ` Peter Stephenson
2009-04-28 19:19 ` Paul Ackersviller
2009-04-28 19:48 ` Peter Stephenson
2009-04-30 3:01 ` Paul Ackersviller
2009-04-30 8:41 ` Peter Stephenson
2009-04-30 15:58 ` Paul Ackersviller
2009-04-30 16:03 ` Peter Stephenson
2009-05-01 14:52 ` Paul Ackersviller [this message]
2009-05-01 15:18 ` Peter Stephenson
2009-05-05 19:39 ` Paul Ackersviller
2009-05-06 19:22 ` Peter Stephenson
2009-05-06 21:50 ` Paul Ackersviller
2009-05-07 15:38 ` Peter Stephenson
2009-05-07 16:02 ` Peter Stephenson
2009-05-07 22:08 ` Paul Ackersviller
2009-05-07 23:30 ` Modules on HP-UX (Re: D07multibyte.ztst failure on HP-UX 11.11) Bart Schaefer
2009-05-08 8:34 ` Peter Stephenson
2009-05-08 14:20 ` Bart Schaefer
2009-05-08 14:29 ` Peter Stephenson
[not found] ` <090508084125.ZM17697@torch.brasslantern.com>
2009-05-11 8:52 ` Peter Stephenson
2009-05-08 18:42 ` Modules on HP-UX Paul Ackersviller
2009-05-12 20:22 ` Modules on HP-UX, with small PATCH Paul Ackersviller
2009-05-08 14:23 ` D07multibyte.ztst failure on HP-UX 11.11 Peter Stephenson
2009-05-02 1:00 ` Phil Pennock
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=20090501145253.GA5070@svalbard \
--to=pda@sdf.lonestar.org \
--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).