This is the mail archive of the
mailing list for the GDB project.
Re: [patch/rfc] Remove all setup_xfail's from testsuite/gdb.mi/
- From: Andrew Cagney <ac131313 at redhat dot com>
- To: Daniel Jacobowitz <drow at mvista dot com>
- Cc: gdb-patches at sources dot redhat dot com
- Date: Thu, 24 Oct 2002 15:29:56 -0400
- Subject: Re: [patch/rfc] Remove all setup_xfail's from testsuite/gdb.mi/
- References: <3DB83EC1.firstname.lastname@example.org> <20021024190956.GA20879@nevyn.them.org>
I believe that you're free to start kfailing things :-)
On Thu, Oct 24, 2002 at 02:41:05PM -0400, Andrew Cagney wrote:
GDB's testsuite is known to be full of xfails that are really kfails or
testsuite bugs. Rather than try to audit each xfail in turn, the
proposal as been to rip out all the xfails (creating a clean slate) and
start marking up the tests from scratch - two steps forward but first
one step back.
I figure I might as well try to get the ball rolling on this and find
out just how much real resistance there is going to be to a change like
this. To that end, this removes all xfail's from the gdb.mi testsuite.
Similar tests, for the other directories, would follow.
I'm known to be a testsuite nazi - I really, really dislike the current
failure levels, and people aren't doing much about it. I'm all in
favor of getting the ball rolling. But are you planning to do the
marking promptly, or just make us stare at even more MI failures for a
while? I've been staring at the mi-console one for a year...
As for me doing the kfail's, the chances of me getting back to that
short term are, lets say, pretty remote. I'm just trying to get the
process started - eliminate the task that's going to cop the most flack :-)
I know it's not practical to do them completely without getting the
testsuite run on a lot of systems, by a lot of people. But you can do
a fair first-order approximation without that.