From: Vin Shelton <acs@alumni.princeton.edu>
To: zsh-workers@zsh.org
Subject: Fwd: Test Failure
Date: Tue, 19 Jan 2010 17:46:43 -0500 [thread overview]
Message-ID: <20a807211001191446y4a16143eg3014207f8c8e609c@mail.gmail.com> (raw)
In-Reply-To: <20a807211001191445x5924b63frc6916febda023502@mail.gmail.com>
Dear zsh-workers,
Since 2010-01-17, I've been getting a failure in the test suite:
: build/zsh-2010-01-17 Tue 19 16:09; make check
**************************************
37 successful test scripts, 1 failure, 0 skipped
**************************************
make[1]: *** [check] Error 1
make[1]: Leaving directory `/home/opt/build/zsh-2010-01-17/Test'
make: *** [check] Error 2
C02 doesn't report an error, but it doesn't report a pass, either.
Here is the tail of the test C02 run with verbosity = 2 (the entire
trace bounced because the message was too big). Please let me know if
you need more info.
- Vin
Running test: argument checking for test builtin
ZTST_test: expecting status: 1
Input: /tmp/zsh.ztst.in.6558, output: /tmp/zsh.ztst.out.6558, error:
/tmp/zsh.ztst.terr.6558
ZTST_execchunk: status 1
ZTST_test: test produced standard output:
ZTST_test: and standard error:
(eval):test:1: too many arguments
Test successful.
ZTST_test: looking for new test
ZTST_test: examining line:
ZTST_test: examining line:
[ -n foo -a -n bar scrimble ]
ZTST_getchunk: read code chunk:
[ -n foo -a -n bar scrimble ]
ZTST_test: examining line:
?(eval):[:1: too many arguments
ZTST_getredir: read redir for '?':
(eval):[:1: too many arguments
ZTST_test: examining line:
Running test: argument checking for [ builtin
ZTST_test: expecting status: 1
Input: /tmp/zsh.ztst.in.6558, output: /tmp/zsh.ztst.out.6558, error:
/tmp/zsh.ztst.terr.6558
ZTST_execchunk: status 1
ZTST_test: test produced standard output:
ZTST_test: and standard error:
(eval):[:1: too many arguments
Test successful.
ZTST_test: looking for new test
ZTST_test: examining line:
ZTST_test: examining line:
test -n foo -a -z "" scramble
ZTST_getchunk: read code chunk:
test -n foo -a -z "" scramble
ZTST_test: examining line:
?(eval):test:1: too many arguments
ZTST_getredir: read redir for '?':
(eval):test:1: too many arguments
ZTST_test: examining line:
Running test: argument checking for test builtin
ZTST_test: expecting status: 1
Input: /tmp/zsh.ztst.in.6558, output: /tmp/zsh.ztst.out.6558, error:
/tmp/zsh.ztst.terr.6558
ZTST_execchunk: status 1
ZTST_test: test produced standard output:
ZTST_test: and standard error:
(eval):test:1: too many arguments
Test successful.
ZTST_test: looking for new test
ZTST_test: examining line:
ZTST_test: examining line:
fn() {
ZTST_getchunk: read code chunk:
fn() {
# careful: first file must exist to trigger bug
[[ -e unmodified ]] || print Where\'s my file\?
[[ unmodified -nt NonExistentFile ]]
print status = $?
}
fn
ZTST_test: examining line:
>status = 1
ZTST_getredir: read redir for '>':
status = 1
ZTST_test: examining line:
Running test: -nt shouldn't abort on non-existent files
ZTST_test: expecting status: 0
Input: /tmp/zsh.ztst.in.6558, output: /tmp/zsh.ztst.out.6558, error:
/tmp/zsh.ztst.terr.6558
ZTST_execchunk: status 0
ZTST_test: test produced standard output:
status = 1
ZTST_test: and standard error:
Test successful.
ZTST_test: looking for new test
ZTST_test: examining line:
ZTST_test: examining line:
if zmodload -i zsh/regex 2>/dev/null; then
ZTST_getchunk: read code chunk:
if zmodload -i zsh/regex 2>/dev/null; then
echo >regex_test.sh 'if [[ $# = 1 ]]; then
if [[ $1 =~ /?[^/]+:[0-9]+:$ ]]; then
:
fi
fi
exit 0'
$ZTST_testdir/../Src/zsh -f ./regex_test.sh
fi
ZTST_test: examining line:
Running test: regex tests shouldn't crash
ZTST_test: expecting status: 0
Input: /tmp/zsh.ztst.in.6558, output: /tmp/zsh.ztst.out.6558, error:
/tmp/zsh.ztst.terr.6558
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:
if zmodload -i zsh/regex 2>/dev/null; then
ZTST_getchunk: read code chunk:
if zmodload -i zsh/regex 2>/dev/null; then
string="this has stuff in it"
bad_regex=0
if [[ $string =~ "h([a-z]*) s([a-z]*) " ]]; then
if [[ "$MATCH $MBEGIN $MEND" != "has stuff 6 15" ]]; then
print -r "regex variables MATCH MBEGIN MEND:
'$MATCH $MBEGIN $MEND'
should be:
'has stuff 6 15'" >&2
bad_regex=1
else
results=("as 7 8" "tuff 11 14")
for i in 1 2; do
if [[ "$match[$i] $mbegin[$i] $mend[$i]" != $results[i] ]]; then
print -r "regex variables match[$i] mbegin[$i] mend[$i]:
'$match[$i] $mbegin[$i] $mend[$i]'
should be
'$results[$i]'" >&2
break
fi
done
fi
else
print -r "regex failed to match '$string'" >&2
fi
(( bad_regex )) || print OK
else
# if it didn't load, tough, but not a test error
print OK
fi
ZTST_test: examining line:
>OK
ZTST_getredir: read redir for '>':
OK
ZTST_test: examining line:
Running test: MATCH, MBEGIN, MEND, match, mbegin, mend
ZTST_test: expecting status: 0
Input: /tmp/zsh.ztst.in.6558, output: /tmp/zsh.ztst.out.6558, error:
/tmp/zsh.ztst.terr.6558
**************************************
0 successful test scripts, 1 failure, 0 skipped
**************************************
make[1]: Leaving directory `/home/opt/build/zsh-2010-01-17/Test'
Regards,
Vin
next parent reply other threads:[~2010-01-19 22:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20a807211001191316x79ce2ffeib91fdc59cdfcb189@mail.gmail.com>
[not found] ` <20a807211001191342i4b1d8d63o9bede714f1831477@mail.gmail.com>
[not found] ` <20a807211001191445x5924b63frc6916febda023502@mail.gmail.com>
2010-01-19 22:46 ` Vin Shelton [this message]
2010-01-20 10:34 ` Peter Stephenson
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=20a807211001191446y4a16143eg3014207f8c8e609c@mail.gmail.com \
--to=acs@alumni.princeton.edu \
--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).