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
- To: gcc at gcc dot gnu dot org
- Subject: Re: Testsuite policy - test case now passes but bug remains
- From: Tom Tromey <tromey at cygnus dot com>
- Date: 18 Jun 2000 16:30:30 -0600
- Newsgroups: cygnus.egcs
- Organization: Cygnus Solutions
- References: <200006181642.SAA04025@loewis.home.cs.tu-berlin.de> <20000618125510.20839@cse.cygnus.com> <200006181827.UAA04887@loewis.home.cs.tu-berlin.de> <20000618115511H.mitchell@codesourcery.com>
- Reply-To: tromey at cygnus dot com
>>>>> "Mark" == Mark Mitchell <mark@codesourcery.com> writes:
Mark> It's true that test-cases in the testsuite tend to get
Mark> duplicated.
For libjava we have a policy (informal, but generally followed) that
if the test case came from a PR, then the PR is mentioned in the
ChangeLog and the commit message. Then the commit message ends up in
Gnats, so that anybody else looking at the PR will notice that the
test case has been checked in. We also name test cases after PRs.
We still get duplication, sometimes, but that has been because (1)
some test cases predate this policy, and (2) some bugs get reported
multiple times. For us the duplication is not much of a problem, but
then we have far fewer tests than gcc.
Tom