This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [RFA:] sim-defs.exp: support xfail


> 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.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]