Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@redhat.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: Daniel Jacobowitz <drow@mvista.com>, gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] Remove all setup_xfail's from testsuite/gdb.mi/
Date: Thu, 24 Oct 2002 14:58:00 -0000	[thread overview]
Message-ID: <3DB86D05.6261C67@redhat.com> (raw)
In-Reply-To: <3DB86B1A.8050003@redhat.com>

Andrew Cagney wrote:
> 
> > On Thu, Oct 24, 2002 at 05:22:42PM -0400, Andrew Cagney wrote:
> >
> >> I think the patch, regardless of KFAIL, is still technically correct. It
> >> fixes a bug: the XFAILs are all wrong so removing them changes the
> >> testsuite so that the numbers it reports better reflect reality.  It's
> >> just unfortunate that part of the reality is a jump in testsuite
> >> failures.  Remember, the XFAILs were originally added to artifically
> >> deflate the test failure rate.
> >
> >
> > As you wish.  Michael's already said he just ignores gdb.mi; if it
> > picks up this many new failures, probably so will I.
> 
> So ..., what will happen when I submit an equivalent patch for one of
> the other directories?
> 
>  >  I don't agree
>  > that it's technically correct; the XFAILs were being used for a
>  > slightly suboptimal meaning since KFAIL wasn't available.  They aren't
>  > real failures no matter which way I look at it.
> 
> The ones I know about were real failures that reflected real bugs.  They
> were XFAILed to supress a bug that wasn't going to be fixed.  Grab an
> old GDB and check the comments that go with the a29k XFAILs.  That is
> very different to XFAILing something because it isn't possible to fix.
> 
> >> >  Would it be
> >> > hard to file PRs for all the failures you see and mark them KFAIL?
> >
> >>
> >> I think that would be a step backwards as all it would do is fill the
> >> bug database with reports like ``test failed''.
> >
> >
> > What do you want in the database then?
> 
> An analysis of the bug.
> 
> >> At least this does move things forward - it puts the tesuite in a state
> >> where everyone and everyone can incrementally do the marking.
> >
> >
> > But nobody will...
> 
> In one hit, or here and there?  I know I will.  I just won't be spending
> a solid week reviewing all of them.

Well, so far we've got two nays.  Why don't Daniel and I shut up, 
and wait to see if there are any yays?


  reply	other threads:[~2002-10-24 21:58 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 [this message]
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
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=3DB86D05.6261C67@redhat.com \
    --to=msnyder@redhat.com \
    --cc=ac131313@redhat.com \
    --cc=drow@mvista.com \
    --cc=gdb-patches@sources.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