Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [testsuite] add gdb.cp/gdb1355.exp
Date: Thu, 18 Sep 2003 00:56:00 -0000	[thread overview]
Message-ID: <20030918005612.GA2546@nevyn.them.org> (raw)
In-Reply-To: <200309180053.h8I0rvWc012998@duracef.shout.net>

On Wed, Sep 17, 2003 at 08:53:57PM -0400, Michael Elizabeth Chastain wrote:
> dc> For one thing, it would be an XFAIL, because it's a GCC bug,
> dc> not a GDB bug.
> 
> The test script, gdb.cp/gdb1355.exp, refers to PR gdb/1355.
> gdb/1355 is an external PR and it refers to PR gcc/12066.
> So there is a gdb PR in there.
> 
> dc> For another thing, though, the bug in question has been fixed,
> dc> so we don't expect it to fail: if it does, it should show up as a FAIL.
> 
> This has been a controversy in the past, too.
> 
> My view is that "KFAIL" means "Known FAIL", which basically means
> there is a PR for it (the PR is the locus of knowledge).

I don't think that was the consensus.  KFAILs are known failures of the
tool under test, i.e. bugs in it.  This is a problem in GDB's input. 
That makes it an xfail.

> dc> I would leave in the new test, with branches and comments as is,
> dc> but I would change all the occurrences of kfail to fail.
> 
> I prefer gdb1355.exp the way it is but I would be okay with that change
> if other people want it that way.
> 
> Michael C
> 

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2003-09-18  0:56 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-18  0:54 Michael Elizabeth Chastain
2003-09-18  0:56 ` Daniel Jacobowitz [this message]
2003-09-18  1:20   ` David Carlton
2003-09-18  1:27     ` David Carlton
  -- strict thread matches above, loose matches on Subject: below --
2003-09-20 22:03 Michael Elizabeth Chastain
2003-09-20 21:59 Michael Elizabeth Chastain
2003-09-18 21:27 Michael Elizabeth Chastain
2003-09-20 21:46 ` Andrew Cagney
2003-09-20 22:31   ` Daniel Jacobowitz
2003-09-21  0:51     ` Andrew Cagney
2003-09-18 21:22 Michael Elizabeth Chastain
2003-09-18 15:33 Michael Elizabeth Chastain
2003-09-20 21:40 ` Andrew Cagney
2003-09-18  2:01 Michael Elizabeth Chastain
2003-09-18 14:27 ` Andrew Cagney
2003-09-18 16:05   ` David Carlton
2003-09-18 15:38 ` David Carlton
2003-09-18  0:00 Michael Elizabeth Chastain
2003-09-18  0:48 ` David Carlton

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=20030918005612.GA2546@nevyn.them.org \
    --to=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