From: Vladimir Prus <ghost@cs.msu.su>
To: gdb@sources.redhat.com
Subject: Re: XFAIL vs. KFAIL
Date: Sat, 05 Apr 2008 18:52:00 -0000 [thread overview]
Message-ID: <ft8aup$9l4$1@ger.gmane.org> (raw)
In-Reply-To: <20080405164927.GB16109@adacore.com>
Joel Brobecker wrote:
>> can somebody explain the difference between XFAILing and KFAILing a
>> test in the GDB testsuite? I've looked at DejaGNU manual, I haven't
>> found the answer.
>
> KFAIL is when we know of a failure caused by a bug in GDB.
>
> XFAIL is when a problem outside of GDB's control is causing the test
> to fail. For instance, a kernel issue, or some wrong debugging info
> generated by the compiler, etc.
Hmm, it appears that at least MI testsuite routinely uses XFAIL for what is
a GDB issue/limitation.
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.
- Volodya
next prev parent reply other threads:[~2008-04-05 16:56 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 [this message]
2008-04-06 0:58 ` Daniel Jacobowitz
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='ft8aup$9l4$1@ger.gmane.org' \
--to=ghost@cs.msu.su \
--cc=gdb@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