This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Testsuite policy - test case now passes but bug remains
On Sun, Jun 18, 2000 at 06:42:42PM +0200, Martin v. Loewis wrote:
> > I'm pretty certain that the original bug is still there, as the failure is
> > the same. It's just that it is no longer triggered in the original reduced
> > testcase. Trivial and apparently unrelated changes to the testcase
> > retrigger the problem - essentially declaring another unused array in the
> > subroutine.
>
> One thing that hasn't been mentioned: The testsuite is *not* a place
> to keep track of bug reports - GNATS is the place for that.
>
> So I think new test cases should *only* be added when a bug had been
> fixed (or, at the discretion of maintainers, for any other reason they
> please), to make sure that the same bug does not re-occur. Adding a
> test case on its own (i.e. without knowing the fix for the testcase)
> is pointless, IMO.
And IMHO, not adding a bug to the testsuite until it is fixed, will insure that
it probably takes longer to fix the bug (since it isn't a daily irritant in
terms of failing tests). I can't speak for other developers, but for me, it
certainly improves the chance I will look at said bug.
--
Michael Meissner, Red Hat, Inc.
PMB 198, 174 Littleton Road #3, Westford, Massachusetts 01886, USA
Work: meissner@redhat.com phone: +1 978-486-9304
Non-work: meissner@spectacle-pond.org fax: +1 978-692-4482