This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Using bugzilla to track XFAILs
- From: Mark Mitchell <mark at codesourcery dot com>
- To: Giovanni Bajo <giovannibajo at libero dot it>
- Cc: gcc at gcc dot gnu dot org, Gabriel Dos Reis <gdr at integrable-solutions dot net>, Zack Weinberg <zack at codesourcery dot com>
- Date: Fri, 13 Feb 2004 13:07:09 -0800
- Subject: Re: Using bugzilla to track XFAILs
- Organization: CodeSourcery, LLC
- References: <061501c3f23d$a464c460$aa422597@bagio>
Giovanni Bajo wrote:
Hello,
it looks like we currently don't have any way to track regressions which are
XFAILed in the testsuite.
Yes, there should be PRs for such things.
I don't see any reason for using a special keyword in Bugzila.
Bugs that happen to already have an XFAILed test in the testsuite are no
different than any other bug, except that we don't have to create a new
test when we fix the bug. The PR should just say "g++.foo/bar/baz.C is
an XFAILed test for this case."
Fundamentally, this problem comes from the fact that some people have
used the testsuite as an alternative to a bug-tracking database. We are
not supposed to be doing that any more; the testsuite is for regression
tests; Bugzilla is for defect-tracking. Things like KFAIL are a bad
idea because they perpetuate this confusion.
--
Mark Mitchell
CodeSourcery, LLC
(916) 791-8304
mark@codesourcery.com