From: Andrew Cagney <ac131313@redhat.com>
To: dejagnu@gnu.org
Cc: gdb@sources.redhat.com, Fernando Nasser <fnasser@redhat.com>
Subject: Print KFAIL's in dejagnu summary?
Date: Thu, 25 Sep 2003 21:56:00 -0000 [thread overview]
Message-ID: <3F7361BB.1000706@redhat.com> (raw)
Hello,
At present KFAILs are supressed from the summary output (the stuff on
the terminal from "make check"). I'd like to change this so that
KFAILs, just like FAILs, are included in the summary. A KFAIL, just
like a FAIL, indicates a bug in the system under test, and hence should
be included in the summary.
Having seen this feature in action for a year now, I think it's
reasonable to conclude that people are ignoring KFAILed tests just like
they ignored GDB's bogus XFAIL tests that went before.
This would mean that any summary output - XPASS, KFAIL, KPASS, and ERROR
would need action.
thoughts?
Andrew
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!
next reply other threads:[~2003-09-25 21:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-25 21:56 Andrew Cagney [this message]
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
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=3F7361BB.1000706@redhat.com \
--to=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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).