public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Geert Bosch <bosch@gnat.com>
To: Zack Weinberg <zack@codesourcery.com>
Cc: guerby@acm.org, gcc@gcc.gnu.org
Subject: Re: ACATS legal status cleared by FSF
Date: Thu, 06 Dec 2001 14:24:00 -0000	[thread overview]
Message-ID: <4DC29618-EA96-11D5-8627-00039344BF4A@gnat.com> (raw)
In-Reply-To: <20011206194008.GE8267@codesourcery.com>

On Thursday, December 6, 2001, at 02:40 , Zack Weinberg wrote:

> I disagree in the strongest possible terms.  Put the B tests in the
> public repository.  If you don't, you only make life harder for people
> outside of ACT who wish to work on the Ada front end.
>
> The maintenance work has to be done anyway, and ought to be the
> responsibility of the person who makes the change that causes the
> tests to regress.  If the B tests are run as part of "make check" in
> the FSF tree, this will be enforced automatically.

I'd like you to first get more familiair with the test suite before
making such strong comments. Laurent and I both have a lot of experience
with this test suite and do not see much value in running the B tests,
whille the cost (in volunteer time) is high.

It is virtually impossible for people to "break" these tests, which
is why I say they are of no value. Even if people *do* manage to break
them (in the hypothetical case that the maintainers would not catch the
error before approving), this will not go unnoticed for a long
time anyway. In the mean time, the *only* programs affected  are 
programs
with fatal errors to start with.

I would be surprised if there would even be consensus to run just
the executable ACATS tests as part of make check, since this would
already double testing time for all contributors. Adding testing
requirements is not free, and there needs to be a benefit to it.

For most of the executable ACATS tests I think there is a good 
benefit/cost
ratio for the front end, and even for the back end. For that reason 
I am happy
to see Laurent doing the work to get them integrated. For the B 
tests, adding
testing is of near-zero value at a high cost.

Zack, I'd like to see very good reasons why you think it is 
reasonable to
significantly increase of required volunteer time to make GNAT changes
and that way hinder development and maintenance.

   -Geert

  reply	other threads:[~2001-12-06 22:12 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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
2001-12-05 15:28 Richard Kenner
2001-12-05 15:41 ` guerby
2001-12-05 23:36 dewar
2001-12-06 15:01 Richard Kenner
2001-12-06 15:40 Richard Kenner
2001-12-06 17:38 dewar
2001-12-06 19:09 dewar
2001-12-07  3:18 Richard Kenner
2001-12-07 17:59 dewar
2001-12-07 18:50 mike stump
2001-12-07 18:57 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-09 14:00 dewar
2001-12-09 15:06 dewar
2001-12-09 15:55 ` Joseph S. Myers
2001-12-09 19:03 dewar

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=4DC29618-EA96-11D5-8627-00039344BF4A@gnat.com \
    --to=bosch@gnat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=guerby@acm.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).