Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Fernando Nasser <fnasser@redhat.com>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: drow@mvista.com, ac131313@cygnus.com, gdb-patches@sources.redhat.com
Subject: Re: [rfa:testsuite} Overhaul sizeof.exp
Date: Wed, 20 Feb 2002 09:42:00 -0000	[thread overview]
Message-ID: <3C73DFE9.885BC65C@redhat.com> (raw)
In-Reply-To: <200202201717.g1KHHYO30993@duracef.shout.net>

Michael Elizabeth Chastain wrote:
> 
> Hmmm, let's start by looking at the alternatives.  Suppose someone writes
> a new test that revels an unexpected bug in gdb (hi Andrew).
> 
> [0] Stqtus quo: we reject the test.

I agree that this is not good.


> [1] FAIL it:  we accept the test and let it FAIL.

Makes it harder for engineers to check if a toolchain is healthy.


> [2] XFAIL it: we accept the test and mark it with XFAIL.

It will be forgotten in the middle of so many other XFAILs.


> [3] KFAIL it: we accept the test and mark it with KFAIL.
> 

With this one you can have a script that produces a "Release Notes"
section with the known bugs by retrieving the bug description from
the database (based on the bug id mentioned in the KFAIL).

The list of KFAILs corresponds to the bugs we all should be trying to 
fix (and that we can fix in GDB independently from any fixes to
compilers,
operation systems, etc.)



> [3] has a problem because KFAIL does not exist.  If the senior maintainers
> decide to approve [3] then I can add it to my analysis tables right away,
> but someone will have to add it to dejagnu.
> 

It is just copy and paste xfail code and add a bit to force the bug id
to be
mandatory.



> I agree with Daniel Jacobowitz; I think [2] is the right thing to do.

This same discussion keeps coming back.  We discovered by trial and
error that XFAILing things only serves to hide them.

But if everybody wants to try again, lets enforce some very stringent
police using the Gnats/Bugzilla database so that the XFAILs are tracked
and removed when the fix is in.



> It's also practical because we can start today.
> 

I don't think this is a good argument.  This has a long time impact 
and we should not do it the "easy" way.  We once xfailed things in
mass and it did not go very well. If we are going to do it lets do
it very cautiously, after discussing how effective our enforcement
police can be.





-- 
Fernando Nasser
Red Hat Canada Ltd.                     E-Mail:  fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario   M4P 2C9


  reply	other threads:[~2002-02-20 17:42 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-20  9:17 Michael Elizabeth Chastain
2002-02-20  9:42 ` Fernando Nasser [this message]
2002-02-20 10:20 ` Andrew Cagney
  -- strict thread matches above, loose matches on Subject: below --
2002-02-20 10:24 Michael Elizabeth Chastain
2002-02-20 11:48 ` Fernando Nasser
2002-02-20  9:49 Michael Elizabeth Chastain
2002-02-20 10:06 ` Fernando Nasser
2002-02-20 10:12   ` Daniel Jacobowitz
2002-02-20 10:07 ` Richard Earnshaw
2002-02-20 10:07 ` Daniel Jacobowitz
2002-02-20 10:18   ` Fernando Nasser
2002-02-20  8:59 Michael Elizabeth Chastain
2002-02-19 20:57 Michael Elizabeth Chastain
2002-02-20  6:57 ` Andrew Cagney
2002-02-20  7:21   ` Andrew Cagney
2002-02-20  8:19     ` Fernando Nasser
2002-02-20 17:57       ` Andrew Cagney
2002-02-20  8:16   ` Fernando Nasser
2002-02-20  8:51     ` Daniel Jacobowitz
2002-02-20  9:24       ` Fernando Nasser
2002-02-21 14:04       ` Jim Blandy
2002-02-21 14:23         ` Daniel Jacobowitz
2002-02-19 20:43 Michael Elizabeth Chastain
2002-02-21 14:03 ` Jim Blandy
2002-02-19 15:46 Michael Elizabeth Chastain
2002-02-19 18:19 ` Andrew Cagney
2002-02-19 15:17 Andrew Cagney

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=3C73DFE9.885BC65C@redhat.com \
    --to=fnasser@redhat.com \
    --cc=ac131313@cygnus.com \
    --cc=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mec@shout.net \
    /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