From: Vin Shelton <acs@alumni.princeton.edu>
To: Daniel Shahaf <d.s@daniel.shahaf.name>
Cc: "Zsh Hackers' List" <zsh-workers@zsh.org>
Subject: Re: pwd -r vs. pwd test failure
Date: Fri, 27 Mar 2020 20:20:49 -0400 [thread overview]
Message-ID: <CACeGjnXuf5=MuAG9DFqhFTa==VLdud7u9db5DsOrB5ZnFqBSSA@mail.gmail.com> (raw)
In-Reply-To: <20200327231118.5fe53e85@tarpaulin.shahaf.local2>
[-- Attachment #1: Type: text/plain, Size: 5486 bytes --]
Yes!
That leaves only a V07 test failure:
ZTST_verbose=2 make TESTNUM=V07 -e check
cd Test ; make check
make[1]: Entering directory '/SSD-2/opt/build/zsh-2020-03-27/Test'
if test -n "gcc"; then \
cd .. && DESTDIR= \
make MODDIR=`pwd`/Test/Modules install.modules > /dev/null; \
fi
if test -z "$ZTST_handler"; then \
ZTST_handler=runtests.zsh; \
fi; \
if ZTST_testlist="`for f in ../../../src/zsh-2020-03-27/Test/V07*.ztst; \
do echo $f; done`" \
ZTST_srcdir="../../../src/zsh-2020-03-27/Test" \
ZTST_exe=../Src/zsh \
../Src/zsh +Z -f ../../../src/zsh-2020-03-27/Test/$ZTST_handler; then \
stat=0; \
else \
stat=1; \
fi; \
sleep 1; \
rm -rf Modules .zcompdump; \
exit $stat
../../../src/zsh-2020-03-27/Test/V07pcre.ztst: starting.
ZTST_getsect: read section name: prep
ZTST_getchunk: read code chunk:
if ! zmodload zsh/pcre 2>/dev/null; then
then
ZTST_unimplemented="the zsh/pcre module was disabled by configure (see
config.modules)"
return 0
fi
setopt rematch_pcre
setopt multibyte
unset -m LC_\*
mb_ok=
langs=(en_{US,GB}.{UTF-,utf}8 en.UTF-8
$(locale -a 2>/dev/null | egrep 'utf8|UTF-8'))
for LANG in $langs; do
if [[ é = ? ]]; then
mb_ok=1
break;
fi
done
if [[ -z $mb_ok ]]; then
ZTST_unimplemented="no UTF-8 locale or multibyte mode is not
implemented"
else
print -u $ZTST_fd Testing PCRE multibyte with locale $LANG
mkdir multibyte.tmp && cd multibyte.tmp
fi
(eval):3: parse error near `ZTST_unimplemented="...'
ZTST_execchunk: status 1
Test ../../../src/zsh-2020-03-27/Test/V07pcre.ztst failed: non-zero status
from preparation code:
if ! zmodload zsh/pcre 2>/dev/null; then
then
ZTST_unimplemented="the zsh/pcre module was disabled by configure (see
config.modules)"
return 0
fi
setopt rematch_pcre
setopt multibyte
unset -m LC_\*
mb_ok=
langs=(en_{US,GB}.{UTF-,utf}8 en.UTF-8
$(locale -a 2>/dev/null | egrep 'utf8|UTF-8'))
for LANG in $langs; do
if [[ é = ? ]]; then
mb_ok=1
break;
fi
done
if [[ -z $mb_ok ]]; then
ZTST_unimplemented="no UTF-8 locale or multibyte mode is not
implemented"
else
print -u $ZTST_fd Testing PCRE multibyte with locale $LANG
mkdir multibyte.tmp && cd multibyte.tmp
fi
../../../src/zsh-2020-03-27/Test/V07pcre.ztst: test failed.
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:
[[ 'foo→bar' =~ .([^[:ascii:]]). ]]
ZTST_getchunk: read code chunk:
[[ 'foo→bar' =~ .([^[:ascii:]]). ]]
print $MATCH
print $match[1]
ZTST_test: examining line:
>o→b
ZTST_getredir: read redir for '>':
o→b
→
ZTST_test: examining line:
Running test: Basic non-ASCII regexp matching
ZTST_test: expecting status: 0
Input: /tmp/zsh.ztst.39712/ztst.in, output: /tmp/zsh.ztst.39712/ztst.out,
error: /tmp/zsh.ztst.39712/ztst.terr
ZTST_execchunk: status 0
ZTST_test: test produced standard output:
0
ZTST_test: and standard error:
(eval):1: failed to compile regex: Invalid character class name
--- /tmp/zsh.ztst.39712/ztst.out 2020-03-27 20:14:42.843332930 -0400
+++ /tmp/zsh.ztst.39712/ztst.tout 2020-03-27 20:14:42.843332930 -0400
@@ -1,2 +1,2 @@
-o→b
-→
+
+0
Test ../../../src/zsh-2020-03-27/Test/V07pcre.ztst failed: output differs
from expected as shown above for:
[[ 'foo→bar' =~ .([^[:ascii:]]). ]]
print $MATCH
print $match[1]
Error output:
(eval):1: failed to compile regex: Invalid character class name
Was testing: Basic non-ASCII regexp matching
../../../src/zsh-2020-03-27/Test/V07pcre.ztst: test failed.
- Vin
On Fri, Mar 27, 2020 at 7:11 PM Daniel Shahaf <d.s@daniel.shahaf.name>
wrote:
> Vin Shelton wrote on Fri, 27 Mar 2020 07:56 -0400:
> > Almost, but not quite:
>
> Does this work better? I added another :P. This catches the case that
> the source directory isn't a realpath. (The case that the _build_
> directory
> isn't a realpath worked since day one.)
>
> 8<--8<--
> From 57818d5fde2334965dce508e239af754f1fa565f Mon Sep 17 00:00:00 2001
> From: Daniel Shahaf <d.s@daniel.shahaf.name>
> Date: Thu, 26 Mar 2020 21:41:49 +0000
> Subject: [PATCH] Fix new test when ${PWD}'s value contains symlinks.
>
> ---
> Test/B13whence.ztst | 11 +++++++----
> 1 file changed, 7 insertions(+), 4 deletions(-)
>
> diff --git a/Test/B13whence.ztst b/Test/B13whence.ztst
> index ea0a4dae5..3b35835fe 100644
> --- a/Test/B13whence.ztst
> +++ b/Test/B13whence.ztst
> @@ -1,7 +1,10 @@
> %prep
>
> mkdir whence.tmp
> - pushd whence.tmp
> + ln -s . whence.tmp/cwd
> + # cd through the symlink in order to test the case that ${prefix} and
> + # ${prefix:P} are different
> + pushd whence.tmp/cwd
> ln -s real step3
> ln -s step3 step2
> ln -s step2 step1
> @@ -16,13 +19,13 @@
> %test
>
> (
> - path=( $PWD/whence.tmp $path )
> + path=( ${PWD:P}/whence.tmp $path )
> whence -S step1
> whence -s step1
> )
> 0q:whence symlink resolution
> ->$prefix/step1 -> $prefix/step2 -> $prefix/step3 -> $prefix/real
> ->$prefix/step1 -> $prefix/real
> +>${prefix:P}/step1 -> ${prefix:P}/step2 -> ${prefix:P}/step3 ->
> ${prefix:P}/real
> +>${prefix:P}/step1 -> ${prefix:P}/real
>
> (
> path=( $PWD/whence.tmp $path )
>
> Cheers,
>
> Daniel
>
next prev parent reply other threads:[~2020-03-28 0:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 12:22 Vin Shelton
2020-03-26 22:02 ` Daniel Shahaf
2020-03-27 11:56 ` Vin Shelton
2020-03-27 23:11 ` Daniel Shahaf
2020-03-28 0:20 ` Vin Shelton [this message]
2020-03-28 0:57 ` Daniel Shahaf
2020-03-28 1:17 ` Vin Shelton
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='CACeGjnXuf5=MuAG9DFqhFTa==VLdud7u9db5DsOrB5ZnFqBSSA@mail.gmail.com' \
--to=acs@alumni.princeton.edu \
--cc=d.s@daniel.shahaf.name \
--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).