From: Jun T <takimoto-j@kba.biglobe.ne.jp>
To: zsh-workers@zsh.org
Subject: Re: A second test release before 5.9 final?
Date: Mon, 2 May 2022 11:24:00 +0900 [thread overview]
Message-ID: <57B00EBA-A66B-4AD8-8546-28210CFB9659@kba.biglobe.ne.jp> (raw)
In-Reply-To: <20220501173858.GA31441@tarpaulin.shahaf.local2>
> 2022/05/02 2:38, Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
>
> --- a/Test/D07multibyte.ztst
> +++ b/Test/D07multibyte.ztst
(snip)
> +0:(workers/50150) zsh/stat with Unicode and metafication
> +>50150-Ą 0
> +>50150-é 0
On macOS this fails as:
Testing multibyte with locale en_US.UTF-8
--- /tmp/zsh.ztst.90230/ztst.out 2022-05-02 10:11:21.000000000 +0900
+++ /tmp/zsh.ztst.90230/ztst.tout 2022-05-02 10:11:21.000000000 +0900
@@ -1,2 +1,2 @@
-50150-Ą 0
50150-é 0
+50150-Ą 0
Test ./D07multibyte.ztst failed: output differs from expected as shown above for:
# Subshell for zmodload isolation
(
zmodload zsh/stat
touch 50150-é 50150-Ą
# Using +size solely in order to make it easier to write the expectations
zstat +size -nor -- 50150-*
)
Was testing: (workers/50150) zsh/stat with Unicode and metafication
It seems macOS uses collating order é < Ą (this may or may not a bug of macOS).
If we need to test the two characters the simplest workaround would be:
zstat +size -nor -- 50150-Ą
zstat +size -nor -- 50150-é
next prev parent reply other threads:[~2022-05-02 2:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-30 18:31 Bart Schaefer
2022-04-30 21:41 ` dana
2022-05-01 14:52 ` Daniel Shahaf
2022-05-01 16:50 ` Bart Schaefer
2022-05-01 17:38 ` Daniel Shahaf
2022-05-02 2:24 ` Jun T [this message]
2022-05-02 3:10 ` Bart Schaefer
2022-05-02 4:09 ` Jun T
2022-05-02 12:58 ` Daniel Shahaf
2022-05-01 17:49 ` Peter Stephenson
2022-05-01 18:09 ` [PATCH] Test for 50101 Bart Schaefer
2022-05-01 19:09 ` [PATCH] Tests for 50126, 50136, and 50149 Bart Schaefer
2022-05-02 4:59 ` Jun T
2022-05-02 5:15 ` Bart Schaefer
2022-05-02 5:46 ` Jun T
2022-05-02 13:14 ` Jun. T
2022-05-02 16:26 ` Bart Schaefer
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=57B00EBA-A66B-4AD8-8546-28210CFB9659@kba.biglobe.ne.jp \
--to=takimoto-j@kba.biglobe.ne.jp \
--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).