From: Hans-Peter Nilsson <hans-peter.nilsson@axis.com>
To: cagney@gnu.org
Cc: hans-peter.nilsson@axis.com, gdb-patches@sources.redhat.com
Subject: Re: [RFA:] sim-defs.exp: support xfail
Date: Wed, 10 Nov 2004 14:55:00 -0000 [thread overview]
Message-ID: <200411101455.iAAEtbqh014407@ignucius.se.axis.com> (raw)
In-Reply-To: <41921F54.7040308@gnu.org> (message from Andrew Cagney on Wed, 10 Nov 2004 09:01:56 -0500)
> Date: Wed, 10 Nov 2004 09:01:56 -0500
> From: Andrew Cagney <cagney@gnu.org>
> Hans-Peter Nilsson wrote:
> > Directly taken from the same option in the ld run_dump_test.
> > Ok to commit?
> > 2004-11-10 Hans-Peter Nilsson <hp@axis.com>
> >
> > * lib/sim-defs.exp (run_sim_test): Support "xfail" option.
>
> What do you mean by "xfail"? (Hint, check a current dejagnu document
> where it describes kfail :-)
I know about kfail, but I'm agnostic. I just mean what happens
for the ld run_dump_test "xfail" option; a simple setup_xfail.
The purpose is to be able to keep failing tests around but not
get the total results marked as partially failing. Reasons for
the failure would be unspecified, matching both xfail and kfail
usage.
To me, it doesn't really matter whether it's kfail or xfail
(vivid descriptions of kfail vs. xfail to /dev/null). In the
sim testsuite I believe it'll be used very sparingly, perhaps
not even for things that are checked in. But it'd be Nice to
Have.
Is the change acceptable by naming the option "kfail" and
calling "setup_kfail"? Or do you want both?
brgds, H-P
PS. BTW, the dejagnu documentation on
<URL:http://www.gnu.org/software/dejagnu/manual/> is not
current; KFAIL isn't mentioned there.
next prev parent reply other threads:[~2004-11-10 14:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-10 9:52 Hans-Peter Nilsson
2004-11-10 14:03 ` Andrew Cagney
2004-11-10 14:55 ` Hans-Peter Nilsson [this message]
2004-11-10 16:40 ` Andrew Cagney
2004-11-16 16:22 ` Hans-Peter Nilsson
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=200411101455.iAAEtbqh014407@ignucius.se.axis.com \
--to=hans-peter.nilsson@axis.com \
--cc=cagney@gnu.org \
--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