From: Daniel Jacobowitz <drow@false.org>
To: Vladimir Prus <ghost@cs.msu.su>
Cc: gdb@sources.redhat.com
Subject: Re: XFAIL vs. KFAIL
Date: Sun, 06 Apr 2008 00:58:00 -0000 [thread overview]
Message-ID: <20080405185156.GA13805@caradoc.them.org> (raw)
In-Reply-To: <ft8aup$9l4$1@ger.gmane.org>
On Sat, Apr 05, 2008 at 08:55:55PM +0400, Vladimir Prus wrote:
> Hmm, it appears that at least MI testsuite routinely uses XFAIL for what is
> a GDB issue/limitation.
KFAIL is relatively new. What I mean by that is it's about five years
old, but the MI testsuite is older.
Most of the XFAILs in the testsuite are bogus at this point.
> Is the distinction really useful? Both seem to be a mechanism to "hide"
> failures that are known to be immediately fixeable, and exact description
> of the problem belongs to a comment, anyway.
No, that's exactly what XFAIL isn't for. We use XFAIL for problems
that we can't fix, like known bugs in versions of GCC or Linux or HP-UX.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-04-05 18:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-05 16:45 Vladimir Prus
2008-04-05 17:13 ` Joel Brobecker
2008-04-05 18:52 ` Vladimir Prus
2008-04-06 0:58 ` Daniel Jacobowitz [this message]
2008-04-07 19:13 ` Michael Snyder
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=20080405185156.GA13805@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=ghost@cs.msu.su \
/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