From: Rob Savoye <rob@welcomehome.org>
To: Andrew Cagney <ac131313@redhat.com>
Cc: dejagnu@gnu.org, gdb@sources.redhat.com,
Fernando Nasser <fnasser@redhat.com>
Subject: Re: Print KFAIL's in dejagnu summary?
Date: Fri, 03 Oct 2003 15:52:00 -0000 [thread overview]
Message-ID: <20031003094742.L12938@welcomehome.org> (raw)
In-Reply-To: <3F7361BB.1000706@redhat.com>; from Andrew Cagney on Thu, Sep 25, 2003 at 05:44:27PM -0400
On Thu, Sep 25, 2003 at 05:44:27PM -0400, Andrew Cagney wrote:
> PS: Some [non] history. Neither Fernando nor I can figure out how/why
> the current behavior came to be. Our best guess is that there was some
> flip-flopping (the lists suggest this) and the current behavior was
> chosen because it happened to be that way in the last version of the
> patch. Enjoy!
I think you're right. It's the way it is, cause that's the way it is...
I think KFAILs should go in the summary. I've never really liked the idea of
either XFAIL or KFAIL, but understand others find these useful. I worry that
once setup as a expected failure, they'll get lost, and never fixed. So KFAIL
should be in the summary to beat developers over the head with them so they
eventually get fixed and removed.
btw - I'm still waiting for KFAIL documentation... :-)
- rob -
next prev parent reply other threads:[~2003-10-03 15:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-25 21:56 Andrew Cagney
2003-09-26 0:03 ` David Carlton
2003-09-27 15:46 ` Andrew Cagney
2003-09-29 19:46 ` David Carlton
2003-09-27 10:34 ` Jim Blandy
2003-10-03 15:52 ` Rob Savoye [this message]
2003-09-25 22:13 Michael Elizabeth Chastain
2003-09-29 20:05 Michael Elizabeth Chastain
2003-10-03 15:57 Michael Elizabeth Chastain
2003-10-03 16:06 ` Rob Savoye
2003-10-03 23:28 ` Ben Elliston
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=20031003094742.L12938@welcomehome.org \
--to=rob@welcomehome.org \
--cc=ac131313@redhat.com \
--cc=dejagnu@gnu.org \
--cc=fnasser@redhat.com \
--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