From: Zack Weinberg <zack@codesourcery.com>
To: Ben Elliston <bje@redhat.com>
Cc: Mike Stump <mstump@apple.com>, gcc@gcc.gnu.org
Subject: Re: A testcase library
Date: Mon, 23 Dec 2002 14:00:00 -0000 [thread overview]
Message-ID: <87el88whpq.fsf@egil.codesourcery.com> (raw)
In-Reply-To: <m3bs3co3f5.fsf@scooby.brisbane.redhat.com> (Ben Elliston's message of "24 Dec 2002 08:01:34 +1100")
Ben Elliston <bje@redhat.com> writes:
> I think that KFAIL clarifies the situation (although I, too, have my
> reservations about having too many test states). It seems few people
> properly understood the purpose of XFAIL, but most instances of XFAIL
> are used to express known failures (take the G++ testsuite for
> example). The number of times XFAIL should be used should be
> comparatively few.
Can you expand on the difference between KFAIL and XFAIL, please? I
don't have this new dejagnu version and from over here it sounds like
a distinction without a difference.
zw
next prev parent reply other threads:[~2002-12-23 21:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2002-12-23 15:27 ` Daniel Jacobowitz
2002-12-20 15:01 ` Joseph S. Myers
2002-12-23 18:08 Richard Kenner
2002-12-24 12:30 ` David Carlton
2002-12-23 18:42 Richard Kenner
2002-12-23 21:57 ` Daniel Jacobowitz
2002-12-24 12:28 ` 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=87el88whpq.fsf@egil.codesourcery.com \
--to=zack@codesourcery.com \
--cc=bje@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=mstump@apple.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).