From: Ray Andrews <rayandrews@eastlink.ca>
To: Bart Schaefer <schaefer@brasslantern.com>, zsh-workers@zsh.org
Subject: Re: zsh-5.2-test-3
Date: Sat, 10 Dec 2016 19:26:49 -0800 [thread overview]
Message-ID: <584CC779.7000207@eastlink.ca> (raw)
In-Reply-To: <161210190737.ZM11109@torch.brasslantern.com>
[-- Attachment #1: Type: text/plain, Size: 4219 bytes --]
On 12/10/2016 07:07 PM, Bart Schaefer wrote:
> What is the platform where you are compiling?
Debian testing in a rather old state of update
> } $ make check
> }
> } ./V10private.ztst: starting.
> } Pattern match failed:
> }
> }
>
> There ought to be more output than that ... please run
>
> $ ZTST_verbose=2 make check TESTNUM=V10
Verbose is right!:
9 /aMisc/Zsh-new/zsh-5.2-test-3 2$ ZTST_verbose=2 make check TESTNUM=V10
cd Test ; make check
make[1]: Entering directory '/aMisc/Zsh-new/zsh-5.2-test-3/Test'
if test -n "gcc"; then \
cd .. && DESTDIR= \
make MODDIR=`pwd`/Test/Modules install.modules > /dev/null; \
fi
if ZTST_testlist="`for f in ./V10*.ztst; \
do echo $f; done`" \
ZTST_srcdir="." \
ZTST_exe=../Src/zsh \
../Src/zsh +Z -f ./runtests.zsh; then \
stat=0; \
else \
stat=1; \
fi; \
sleep 1; \
rm -rf Modules .zcompdump; \
exit $stat
./V10private.ztst: starting.
ZTST_getsect: read section name: prep
ZTST_getchunk: read code chunk:
if ! zmodload zsh/param/private 2>/dev/null; then
ZTST_unimplemented="can't load the zsh/param/private module for
testing"
else
# Do not use .tmp here, ztst.zsh will remove it too soon (see
%cleanup)
mkdir private.TMP
sed -e 's,# test_zsh_param_private,zmodload zsh/param/private,'
< $ZTST_srcdir/B02typeset.ztst > private.TMP/B02
fi
ZTST_execchunk: status 0
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:
(zmodload -u zsh/param/private && zmodload zsh/param/private)
ZTST_getchunk: read code chunk:
(zmodload -u zsh/param/private && zmodload zsh/param/private)
ZTST_test: examining line:
Running test: unload and reload the module without crashing
ZTST_test: expecting status: 0
Input: /tmp/zsh.ztst.8681/ztst.in, output:
/tmp/zsh.ztst.8681/ztst.out, error: /tmp/zsh.ztst.8681/ztst.terr
ZTST_execchunk: status 0
ZTST_test: test produced standard output:
ZTST_test: and standard error:
Test successful.
ZTST_test: looking for new test
ZTST_test: examining line:
ZTST_test: examining line:
ZTST_verbose=0 $ZTST_exe +Z -f $ZTST_srcdir/ztst.zsh private.TMP/B02
ZTST_getchunk: read code chunk:
ZTST_verbose=0 $ZTST_exe +Z -f $ZTST_srcdir/ztst.zsh private.TMP/B02
ZTST_test: examining line:
*>*
ZTST_getredir: read redir for '>':
*
ZTST_test: examining line:
*>*
ZTST_getredir: read redir for '>':
*
ZTST_test: examining line:
Running test: typeset still works with zsh/param/private module loaded
ZTST_test: expecting status: 0
Input: /tmp/zsh.ztst.8681/ztst.in, output:
/tmp/zsh.ztst.8681/ztst.out, error: /tmp/zsh.ztst.8681/ztst.terr
ZTST_execchunk: status 0
ZTST_test: test produced standard output:
private.TMP/B02: starting.
Test case skipped: cannot test setuid error when tests run as superuser
private.TMP/B02: all tests successful.
ZTST_test: and standard error:
Pattern match failed:
<*
<*
>private.TMP/B02: starting.
>Test case skipped: cannot test setuid error when tests run as
superuser
>private.TMP/B02: all tests successful.
Test ./V10private.ztst failed: output differs from expected as shown
above for:
ZTST_verbose=0 $ZTST_exe +Z -f $ZTST_srcdir/ztst.zsh private.TMP/B02
Was testing: typeset still works with zsh/param/private module loaded
./V10private.ztst: test failed.
ZTST_getsect: read section name: clean
ZTST_getchunk: read code chunk:
rm -r private.TMP
ZTST_execchunk: status 0
ZTST_getchunk: read code chunk:
**************************************
0 successful test scripts, 1 failure, 0 skipped
**************************************
Makefile:187: recipe for target 'check' failed
make[1]: *** [check] Error 1
make[1]: Leaving directory '/aMisc/Zsh-new/zsh-5.2-test-3/Test'
Makefile:263: recipe for target 'check' failed
make: *** [check] Error 2
next prev parent reply other threads:[~2016-12-11 3:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20161206195028epcas2p3c53119ab37952571be3238cdf228d88f@epcas2p3.samsung.com>
[not found] ` <20161206194916.10448440@ntlworld.com>
2016-12-06 23:33 ` test failures on Solaris (was Re: zsh-5.2-test-2) Danek Duvall
2016-12-07 0:36 ` Bart Schaefer
[not found] ` <20161209095729.2033b5be@pwslap01u.europe.root.pri>
[not found] ` <20161209195457.27e43234@ntlworld.com>
[not found] ` <584CB4EF.6070904@eastlink.ca>
2016-12-11 3:07 ` zsh-5.2-test-3 Bart Schaefer
2016-12-11 3:26 ` zsh-5.2-test-3 Daniel Shahaf
2016-12-11 3:33 ` zsh-5.2-test-3 Bart Schaefer
2016-12-11 3:26 ` Ray Andrews [this message]
2016-12-11 3:44 ` zsh-5.2-test-3 Bart Schaefer
2016-12-11 3:59 ` zsh-5.2-test-3 Ray Andrews
2016-12-11 9:36 ` zsh-5.2-test-3 Bart Schaefer
2016-12-11 17:01 ` zsh-5.2-test-3 Ray Andrews
2016-12-11 17:14 ` zsh-5.2-test-3 Bart Schaefer
2016-12-11 4:11 ` zsh-5.2-test-3 Daniel Shahaf
2016-12-11 8:58 ` zsh-5.2-test-3 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=584CC779.7000207@eastlink.ca \
--to=rayandrews@eastlink.ca \
--cc=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).