Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: David Carlton <carlton@kealia.com>
Cc: dejagnu@gnu.org, gdb@sources.redhat.com,
	Fernando Nasser <fnasser@redhat.com>
Subject: Re: Print KFAIL's in dejagnu summary?
Date: Sat, 27 Sep 2003 15:46:00 -0000	[thread overview]
Message-ID: <3F759D90.8050203@redhat.com> (raw)
In-Reply-To: <yf2zngs8qji.fsf@hawaii.kealia.com>

> On Thu, 25 Sep 2003 17:44:27 -0400, Andrew Cagney <ac131313@redhat.com> said:
> 
> 
>> 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.
> 
> 
> I have a mild preference for the current behavior.  Mostly I use the
> summary output to get a feel for whether or not a change of mine has
> obviously gone wrong; the noisier the summary output is, the harder it
> is to use it this way.  Of course, I always search the entire gdb.sum
> for regressions, just to make sure, so it won't make a big practical
> difference to me one way or another.

The numbers at the bottom should tell you that:

- no errors
- no unexpected passes
- no unknown failures.

unfortunatly, the only truely robust way is to compare the .sum files.

Andrew



  reply	other threads:[~2003-09-27 15:46 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 [this message]
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=3F759D90.8050203@redhat.com \
    --to=ac131313@redhat.com \
    --cc=carlton@kealia.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