[-- Attachment #1: Type: text/plain, Size: 3507 bytes --] On my Arch linux x86_64 system, I'm seeing a Y02 test failure. TESTNUM=Y02 ZTST_verbose=1 make check cd Test ; make check make[1]: Entering directory '/opt/build/zsh-2021-10-26/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-2021-10-26/Test/Y02*.ztst; \ do echo $f; done`" \ ZTST_srcdir="../../../src/zsh-2021-10-26/Test" \ ZTST_exe=../Src/zsh \ ../Src/zsh +Z -f ../../../src/zsh-2021-10-26/Test/$ZTST_handler; then \ stat=0; \ else \ stat=1; \ fi; \ sleep 1; \ rm -rf Modules .zcompdump; \ exit $stat ../../../src/zsh-2021-10-26/Test/Y02compmatch.ztst: starting. Running test: Match Error for "z:" Test successful. Running test: Match Error for "m:" Test successful. Running test: Match Error for "M:" Test successful. Running test: Match Error "r:" Test successful. Running test: Match Error "R:" Test successful. Running test: Match Error for "l:" Test successful. Running test: Match Error for "L:" Test successful. Running test: Match Error for "m:{0-9" Test successful. Running test: Match Error for "m:{0-9}" Test successful. Running test: Match Error for "m:{0-9}={" Test successful. Running test: Match Error for "m:{0-9}={0-" Test successful. Running test: Match Error for "m:{0-9}={-" Test successful. Running test: Match Error "r:" Test successful. Running test: Documentation example for options, input "nolistbee" Test successful. Running test: Documentation example for options, input "list_bee" Test successful. Running test: Documentation example for options, input "ListBee" Test successful. Running test: Documentation example for options, input "NOList" Test successful. Running test: Documentation example for options, input "NO_List\t__\tB\t" Test successful. Running test: Documentation example for options, input "__\tN\t__o\t___\tlist_\tbeep__\t" Test successful. Running test: Documentation example for options, input "__\tNo\t___\tlist_\tbeep__\t" Test successful. Running test: Documentation example for options, input "___\tlist_\tbeep__\t" Test successful. Running test: Documentation example for options, input "__no_listbe" Test successful. Running test: Documentation example for options, input "nonono_listbe" Test successful. Running test: Documentation example for lowercase insenitive M, input "ab\tC\t" Test successful. Running test: Documentation example for lowercase insenitive m, input "A\t\t" Test successful. Running test: Documentation example for case insenitive M, input "aB\t\t" Test successful. Running test: Documentation example for case insenitive m, input "aB\t\t" Test successful. Running test: r:|.=* should complete .s.u Test successful. Running test: r:[^.]||.=* should not complete .s.u, but should complete c.s.u Test failed, as expected. Running test: r:|.=* should complete .g. Test ../../../src/zsh-2021-10-26/Test/Y02compmatch.ztst was expected to fail, but passed. Was testing: r:|.=* should complete .g. ../../../src/zsh-2021-10-26/Test/Y02compmatch.ztst: test XPassed. ************************************** 0 successful test scripts, 1 failure, 0 skipped ************************************** make[1]: *** [Makefile:190: check] Error 1 make[1]: Leaving directory '/opt/build/zsh-2021-10-26/Test' make: *** [Makefile:263: check] Error 2 Please let me know if you need any more info. - Vin -- *Never for money, always for love* [-- Attachment #2: Type: text/html, Size: 5069 bytes --]
On Tue, Oct 26, 2021 at 6:51 PM Vin Shelton <acs@alumni.princeton.edu> wrote:
>
> On my Arch linux x86_64 system, I'm seeing a Y02 test failure.
I have the same one, on both MacOs and Ubuntu:
Test ./Y02compmatch.ztst was expected to fail, but passed.
Was testing: r:|.=* should complete .g.
I think this is probably just a typo in the test condition. If I
remove the "f" from "0f" this and all subsequent tests pass.
On macOS: % make TESTNUM=Y01 check if test -n "gcc"; then \ cd .. && DESTDIR= \ /Applications/Xcode.app/Contents/Developer/usr/bin/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 ./Y01*.ztst; \ do echo $f; done`" \ ZTST_srcdir="." \ ZTST_exe=../Src/zsh \ ../Src/zsh +Z -f ./$ZTST_handler; then \ stat=0; \ else \ stat=1; \ fi; \ sleep 1; \ rm -rf Modules .zcompdump; \ exit $stat ./Y01completion.ztst: starting. --- /tmp/zsh.ztst.176/ztst.out 2021-11-12 21:19:31.000000000 +0200 +++ /tmp/zsh.ztst.176/ztst.tout 2021-11-12 21:19:31.000000000 +0200 @@ -1 +1 @@ -line: {ztst.zsh }{} +line: {ztst.zsh}{} Test ./Y01completion.ztst failed: output differs from expected as shown above for: comptesteval "path=( $ZTST_srcdir:A )" comptest $'zt\t' Was testing: command ./Y01completion.ztst: test failed. ************************************** 0 successful test scripts, 1 failure, 0 skipped ************************************** make: *** [check] Error 1
Your subject says Y02 but your text showed Y01. In any case all tests pass for me on both Ubuntu and MacOS. My first suspicion is always a "build tree is not source tree" problem, but from the diff I can't see how that would be it, in this case.
On Fri, Nov 12, 2021 at 9:57 PM Bart Schaefer <schaefer@brasslantern.com> wrote: > > Your subject says Y02 but your text showed Y01. Whoops! It appears workers 49530 got stuck in my head. > In any case all tests > pass for me on both Ubuntu and MacOS. > My first suspicion is always a "build tree is not source tree" > problem, but from the diff I can't see how that would be it, in this > case. I tried it again after doing `make realclean`, etc., from both the repo root and the Test dir. Still fails.
On Fri, Nov 12, 2021 at 1:28 PM Marlon Richert <marlon.richert@gmail.com> wrote:
>
> I tried it again after doing `make realclean`, etc.
Dunno what else to tell you; have you tried increasing ZTST_verbose ?
zsh-5.8-542-gc7f4634
524 make realclean
526 ./Util/preconfig
527 ./configure
528 make
529 make check TESTNUM=Y01
cd Test ; /Applications/Xcode.app/Contents/Developer/usr/bin/make check
if test -n "gcc"; then \
cd .. && DESTDIR= \
/Applications/Xcode.app/Contents/Developer/usr/bin/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 ./Y01*.ztst; \
do echo $f; done`" \
ZTST_srcdir="." \
ZTST_exe=../Src/zsh \
../Src/zsh +Z -f ./$ZTST_handler; then \
stat=0; \
else \
stat=1; \
fi; \
sleep 1; \
rm -rf Modules .zcompdump; \
exit $stat
./Y01completion.ztst: starting.
./Y01completion.ztst: all tests successful.
**************************************
1 successful test script, 0 failures, 0 skipped
**************************************
On Fri, Nov 12, 2021, at 4:49 PM, Bart Schaefer wrote:
> zsh-5.8-542-gc7f4634
>
> 524 make realclean
> 526 ./Util/preconfig
> 527 ./configure
> 528 make
> 529 make check TESTNUM=Y01
This passes for me on macOS as well, in a clean tree.
--
vq
On Sat, Nov 13, 2021 at 12:01 AM Lawrence Velázquez <larryv@zsh.org> wrote:
>
> On Fri, Nov 12, 2021, at 4:49 PM, Bart Schaefer wrote:
> > zsh-5.8-542-gc7f4634
> >
> > 524 make realclean
> > 526 ./Util/preconfig
> > 527 ./configure
> > 528 make
> > 529 make check TESTNUM=Y01
>
> This passes for me on macOS as well, in a clean tree.
It now passes for me, too. No idea what changed. I wonder if something
in my shell environment could have affected it?