From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Lots of test failures when --disable-multibyte
Date: Mon, 4 Apr 2022 15:00:21 -0700 [thread overview]
Message-ID: <CAH+w=7Y7t2Su6sXM6pu-CNUgh2qhwQG+fo3WaKPtmpnJAMn8rg@mail.gmail.com> (raw)
In-Reply-To: <CAH+w=7bWU2MNHN2cv6P3gj+T-o1E6hX7TeB272-4cuqsmnVyKw@mail.gmail.com>
After applying 49989 through 49992, the only remaining** test failure
in single-byte compilation is:
./D04parameter.ztst: starting.
--- /tmp/zsh.ztst.280446/ztst.out 2022-04-04 14:36:24.025587676 -0700
+++ /tmp/zsh.ztst.280446/ztst.tout 2022-04-04 14:36:24.025587676 -0700
@@ -1,4 +1,4 @@
x
+
x
-x
-y
+
Test ./D04parameter.ztst failed: output differs from expected as shown
above for:
a=(1 "" 3)
print -rl -- "${(@)a//*/x}"
a=""
print -rl -- "${(@)a//*/y}"
Was testing: Zero-length string match in parameter substitution
Plus the one immediately after it (Zero-length string match at end).
I'm going to have to leave those one to someone else.
** We might want to consider a ZTST_ mode where we attempt all tests
in a file even if one fails. I confirmed these by marking them "0f"
one by one, but that could become tedious.
next prev parent reply other threads:[~2022-04-04 22:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-04 2:03 Bart Schaefer
2022-04-04 14:43 ` Peter Stephenson
2022-04-04 15:31 ` Bart Schaefer
2022-04-04 16:23 ` Peter Stephenson
2022-04-04 21:10 ` Bart Schaefer
2022-04-04 21:45 ` Bart Schaefer
2022-04-04 22:00 ` Bart Schaefer [this message]
2022-04-05 16:00 ` Bart Schaefer
2022-04-05 16:15 ` Mikael Magnusson
2022-04-05 20:29 ` Peter Stephenson
2022-04-06 3:48 ` Bart Schaefer
2022-04-06 5:32 ` ZTST_continue (was Re: Lots of test failures when --disable-multibyte) Jun T
2022-04-06 13:37 ` Peter Stephenson
2022-04-07 12:33 ` Jun T
2022-04-07 12:34 ` Jun T
2022-04-04 18:52 ` Lots of test failures when --disable-multibyte 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='CAH+w=7Y7t2Su6sXM6pu-CNUgh2qhwQG+fo3WaKPtmpnJAMn8rg@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--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).