From: kenner@vlsi1.ultra.nyu.edu (Richard Kenner)
To: zack@codesourcery.com
Cc: gcc@gcc.gnu.org
Subject: Re: ACATS legal status cleared by FSF
Date: Fri, 07 Dec 2001 03:18:00 -0000 [thread overview]
Message-ID: <10112071106.AA05851@vlsi1.ultra.nyu.edu> (raw)
This is all fair. How about a compromise position where you check the
B tests into the CVS tree but don't bother adding dejagnu harnesses
for them. They are then instantly available if they are needed.
The issue is the *baselines*, not either the B tests themselves or the
test harness. They must be checked in *and* actively maintained if
they are to be "instantly available".
One possibility is to run the B tests in a non-conventional way, where all
the test harness does is to check for the presence of at least one
error line for each line marked ERROR. I don't know how hard such a
harness is to write, and that's not the way B tests are usually done, but
might work.
That would just leave the issue of splits, not baselines, and those change
less often.
next reply other threads:[~2001-12-07 11:12 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-07 3:18 Richard Kenner [this message]
2001-12-07 4:20 ` ACATS B tests guerby
-- strict thread matches above, loose matches on Subject: below --
2001-12-09 19:03 ACATS legal status cleared by FSF dewar
2001-12-09 15:06 dewar
2001-12-09 15:55 ` Joseph S. Myers
2001-12-09 14:00 dewar
2001-12-07 19:12 dewar
2001-12-09 13:02 ` Zack Weinberg
2001-12-09 14:52 ` guerby
2001-12-09 19:47 ` Geert Bosch
2001-12-07 18:57 dewar
2001-12-07 18:50 mike stump
2001-12-07 17:59 dewar
2001-12-06 19:09 dewar
2001-12-06 17:38 dewar
2001-12-06 15:40 Richard Kenner
2001-12-06 15:01 Richard Kenner
2001-12-05 23:36 dewar
2001-12-05 15:28 Richard Kenner
2001-12-05 15:41 ` guerby
2001-12-05 15:13 guerby
2001-12-05 16:21 ` Joseph S. Myers
2001-12-05 18:00 ` Jerry van Dijk
2001-12-06 3:36 ` Geoff Keating
2001-12-06 9:34 ` Geert Bosch
2001-12-06 11:48 ` Zack Weinberg
2001-12-06 14:24 ` Geert Bosch
2001-12-06 14:32 ` Joseph S. Myers
2001-12-06 15:10 ` Zack Weinberg
2001-12-06 15:41 ` Geert Bosch
2001-12-06 18:22 ` Zack Weinberg
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=10112071106.AA05851@vlsi1.ultra.nyu.edu \
--to=kenner@vlsi1.ultra.nyu.edu \
--cc=gcc@gcc.gnu.org \
--cc=zack@codesourcery.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).