From: Andrew Cagney <ac131313@redhat.com>
To: Michael Snyder <msnyder@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] Remove all setup_xfail's from testsuite/gdb.mi/
Date: Thu, 24 Oct 2002 14:32:00 -0000 [thread overview]
Message-ID: <3DB866E7.4010605@redhat.com> (raw)
In-Reply-To: <3DB86394.812BFE78@redhat.com>
> Andrew Cagney wrote:
>
>>
>> Hello,
>>
>> 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 don't know if MI is the best choice to start with.
> Who's going to fix them up? Certainly not me.
>
> Why not pick one or two mainstream tests, from gdb.base, that have a lot
> of xfails in them. Let us get a feel for the pain threshold. Changes
> to gdb.mi don't tell me a thing, because I generally ignore it.
True. For the MI though, I know all the existing XFAILs are bogus so
I'm in a stronger position to argue that they should be removed anyway.
Besides, it appears MI is being worked on at present.
Anyway, it will look like this:
> Before:
>
> === gdb Summary ===
>
> # of expected passes 8298
> # of unexpected failures 60
> # of unexpected successes 10
> # of expected failures 172
> # of unsupported tests 2
>
> After:
>
> === gdb Summary ===
>
> # of expected passes 8308
> # of unexpected failures 232
> # of unsupported tests 2
Andrew.
next prev parent reply other threads:[~2002-10-24 21:32 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-24 11:41 Andrew Cagney
2002-10-24 12:09 ` Daniel Jacobowitz
2002-10-24 12:29 ` Andrew Cagney
2002-10-24 12:58 ` Daniel Jacobowitz
2002-10-24 14:22 ` Andrew Cagney
2002-10-24 14:26 ` Daniel Jacobowitz
2002-10-24 14:39 ` Michael Snyder
2002-10-24 16:31 ` Andrew Cagney
2002-10-24 16:36 ` Michael Snyder
2002-10-24 14:50 ` Andrew Cagney
2002-10-24 14:58 ` Michael Snyder
2002-10-24 15:31 ` Ben Elliston
2002-10-24 16:44 ` Andrew Cagney
2002-10-24 17:35 ` Michael Snyder
2002-10-24 18:25 ` Andrew Cagney
2002-10-24 14:18 ` Michael Snyder
2002-10-24 14:32 ` Andrew Cagney [this message]
2002-10-24 14:39 ` David Carlton
2002-10-24 14:57 ` Andrew Cagney
2002-10-24 15:00 ` Michael Snyder
2002-10-24 15:26 ` David Carlton
2002-10-24 15:36 ` Andrew Cagney
2003-01-15 15:55 ` Andrew Cagney
2003-01-15 17:25 ` Fernando Nasser
2003-01-16 16:53 ` Andrew Cagney
2003-01-16 17:05 ` Daniel Jacobowitz
2003-01-16 19:03 ` Andrew Cagney
2003-01-16 19:55 ` Daniel Jacobowitz
2003-01-15 17:44 Michael Elizabeth Chastain
2003-01-15 17:51 ` Daniel Jacobowitz
2003-01-16 14:27 ` Fernando Nasser
2003-01-16 14:30 ` Daniel Jacobowitz
2003-01-16 14:46 ` Fernando Nasser
2003-01-16 14:52 ` Daniel Jacobowitz
2003-01-16 15:46 ` Andrew Cagney
2003-01-16 14:20 ` Fernando Nasser
2003-01-16 17:07 Michael Elizabeth Chastain
2003-01-16 17:12 Michael Elizabeth Chastain
2003-01-16 20:06 Michael Elizabeth Chastain
2003-01-16 20:12 ` Daniel Jacobowitz
2003-01-17 14:12 ` Fernando Nasser
2003-01-17 16:05 ` Andrew Cagney
2003-01-17 14:26 ` Fernando Nasser
2003-01-17 19:00 Michael Elizabeth Chastain
2003-01-17 19:16 ` David Carlton
2003-01-17 19:20 ` David Carlton
2003-01-17 19:30 ` Daniel Jacobowitz
2003-01-17 19:28 ` Andrew Cagney
2003-01-17 19:28 Michael Elizabeth Chastain
2003-01-17 19:34 ` Daniel Jacobowitz
2003-01-17 19:32 Michael Elizabeth Chastain
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=3DB866E7.4010605@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=msnyder@redhat.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