From: kenner@vlsi1.ultra.nyu.edu (Richard Kenner)
To: drow@mvista.com
Cc: gcc@gcc.gnu.org
Subject: Re: A testcase library
Date: Mon, 23 Dec 2002 18:42:00 -0000 [thread overview]
Message-ID: <10212240145.AA23279@vlsi1.ultra.nyu.edu> (raw)
Suppose that GDB is debugging a program, and the information it needs
is simply missing from the debug info. Zilch, nada, absolutely no way
to recover it. That's an XFAIL.
Suppose that a testcase is for a new bug that no one's figured out how
to fix yet. That's a KFAIL. All KFAILs are required to have an open PR
associated with them, at least in GDB-land.
The difference, in theory, is that KFAILs represent real problems that
have not been fixed; and XFAILs represent "expected" failures, problems
in the system or tools that can not be fixed in the program-under-test.
I still don't get it. Your first example sounds like something that's not
a bug at all, in which case why would the "test case" still be in the suite?
next reply other threads:[~2002-12-24 1:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-23 18:42 Richard Kenner [this message]
2002-12-23 21:57 ` Daniel Jacobowitz
2002-12-24 12:28 ` David Carlton
-- strict thread matches above, loose matches on Subject: below --
2002-12-23 18:08 Richard Kenner
2002-12-24 12:30 ` David Carlton
2002-12-20 8:12 Volker Reichelt
2002-12-20 8:14 ` Jakub Jelinek
2002-12-20 8:50 ` Volker Reichelt
2002-12-20 9:12 ` Eric Botcazou
2002-12-20 9:32 ` Wolfgang Bangerth
2002-12-20 10:51 ` Volker Reichelt
2002-12-20 12:02 ` Jason R Thorpe
2002-12-22 22:44 ` Ben Elliston
2002-12-23 12:46 ` Mike Stump
2002-12-23 12:57 ` Daniel Jacobowitz
2002-12-23 15:54 ` Mike Stump
2002-12-23 16:35 ` Daniel Jacobowitz
2002-12-23 13:50 ` Ben Elliston
2002-12-23 14:00 ` Zack Weinberg
2002-12-23 15:27 ` Daniel Jacobowitz
2002-12-20 15:01 ` Joseph S. Myers
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=10212240145.AA23279@vlsi1.ultra.nyu.edu \
--to=kenner@vlsi1.ultra.nyu.edu \
--cc=drow@mvista.com \
--cc=gcc@gcc.gnu.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).