From: "Vin Shelton" <acs@alumni.princeton.edu>
To: "Zsh hackers list" <zsh-workers@sunsite.dk>
Subject: Test issues
Date: Tue, 11 Jul 2006 10:49:09 -0400 [thread overview]
Message-ID: <20a807210607110749q205d2d07n5b6957098a3ca5a1@mail.gmail.com> (raw)
Greetings -
I'd like to bring up a few issues with the test scripts:
1. Since yesterday, the A04 test has been failing on my linux systems
at home (kubuntu) and at work (RHEL). Here's the tail of
'ZTST_verbose=3 TESTNUM=A04 make test':
Running test: Using {fdvar}> syntax to open a new file descriptor
ZTST_test: expecting status: 0
Input: /tmp/zsh.ztst.in.26465, output: /tmp/zsh.ztst.out.26465, error:
/tmp/zsh.ztst.terr.26465
make: [test] Error 127 (ignored)
Please let me know if you need more diagnostic input.
2. Peter, thanks for implementing the multibyte test. There's a very
minor typo:
Index: Test/D07multibyte.ztst
===================================================================
RCS file: /cvsroot/zsh/zsh/Test/D07multibyte.ztst,v
retrieving revision 1.5
diff -u -r1.5 D07multibyte.ztst
--- Test/D07multibyte.ztst 10 Jul 2006 13:08:24 -0000 1.5
+++ Test/D07multibyte.ztst 11 Jul 2006 14:17:52 -0000
@@ -12,7 +12,7 @@
fi
done
if [[ -z $mb_ok ]]; then
- ZTST_unimplemented="no UTF-8 locale or multibyte mode is not implemnted"
+ ZTST_unimplemented="no UTF-8 locale or multibyte mode is not implemented"
else
print Testing multibyte with locale $LANG >&8
fi
3. Is there a relliable way to get the number of test failures? In
case #1 above, the output of 'make check' looks like this:
/usr/local/src/zsh-2006-07-11/Test/A03quoting.ztst: starting.
/usr/local/src/zsh-2006-07-11/Test/A03quoting.ztst: all tests successful.
/usr/local/src/zsh-2006-07-11/Test/A04redirect.ztst: starting.
/usr/local/src/zsh-2006-07-11/Test/A05execution.ztst: starting.
/usr/local/src/zsh-2006-07-11/Test/A05execution.ztst: all tests successful.
Note that there's no failure message printed for A04. What I'm
currently doing is using 'grep -c' to count 'starting' and then
counting 'skipped' and 'successful'. Currently, my math looks like
this: #failures = #starts - #successful - #skipped. Is there a better
way?
Peter - I think the test suite is very helpful - thanks for creating it!
Thanks,
Vin
--
Whoever you are, no matter how lonely,
the world offers itself to your imagination,
calls to you like the wild geese, harsh and exciting--
over and over announcing your place
in the family of things. Mary Oliver
next reply other threads:[~2006-07-11 14:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-11 14:49 Vin Shelton [this message]
2006-07-11 15:29 ` Peter Stephenson
2006-07-11 16:23 ` Bart Schaefer
2006-07-12 11:48 ` Peter Stephenson
2006-07-13 9:37 ` Bart Schaefer
2006-07-11 15:34 ` 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=20a807210607110749q205d2d07n5b6957098a3ca5a1@mail.gmail.com \
--to=acs@alumni.princeton.edu \
--cc=zsh-workers@sunsite.dk \
/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).