From: Anthony Green <green@cygnus.com>
To: mauve-discuss@sourceware.cygnus.com
Subject: New files checked in.
Date: Thu, 01 Apr 1999 00:00:00 -0000 [thread overview]
Message-ID: <199903141705.JAA25942@hoser.cygnus.com> (raw)
Message-ID: <19990401000000.7kRSwZORRYGn3JGqOPTl1kiUkxiG_OhjCEa373-TaH4@z> (raw)
I've checked in a few of the new tests from HP. Andrew Haley did the
initial conversion to make them work in our framework.
If you run them, you'll see that the test count isn't significantly
higher than before. It has to do with how the tests are counted.
Their code tries all kinds of things and only register failures when
they happen, whereas we like to keep track of `passes' as well. My
hope is that that these files will slowly migrate over to using the
harness.check methods rather than just harness.fail. If anyone feels
inspired, that would be very helpful.
There's plenty more to say, but I have to run. More later.
AG
--
Anthony Green Cygnus Solutions
Sunnyvale, California
next reply other threads:[~1999-04-01 0:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-14 9:05 Anthony Green [this message]
1999-04-01 0:00 ` Anthony Green
1999-04-01 4:02 ` Andrew Haley
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=199903141705.JAA25942@hoser.cygnus.com \
--to=green@cygnus.com \
--cc=mauve-discuss@sourceware.cygnus.com \
/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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).