Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Gdb List <gdb@sources.redhat.com>
Subject: Re: Running the test suite
Date: Fri, 28 Sep 2001 12:50:00 -0000	[thread overview]
Message-ID: <20010928155059.A17925@nevyn.them.org> (raw)
In-Reply-To: <87y9mzgket.fsf@creche.redhat.com>

On Fri, Sep 28, 2001 at 01:55:22PM -0600, Tom Tromey wrote:
> I ran the gdb test suite today.  I get more than a few errors (211
> FAIL).  I'd like to know whether these errors come from my hacks or
> are just expected.
> 
> Is there some "standard" number of fails I should expect?
> 
> Soon I'll back out my patches, run the test suite, and then compare
> results.  That's a pain though.

In general, the testsuite is exceedingly sensitive to compiler changes;
hopefully someday we'll put together XFAILs in such a way that we can
have no failures, or at least document a few platforms that pass.

For comparison, here's a clean testsuite run on i386-linux, with gcc
2.95.3 (+ Debian/unstable patches):

# of expected passes            7560
# of unexpected failures        143
# of unexpected successes       32
# of expected failures          192
# of unresolved testcases       104
# of untested testcases         6

And with a couple of testsuite patches I've posted today, and one
mildly destabilizing patch that I'm working on:
# of expected passes            7570
# of unexpected failures        134
# of unexpected successes       34
# of expected failures          190
# of unresolved testcases       104
# of untested testcases         6


The best you can do right now is to run the testsuite before and after
patches.

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


      reply	other threads:[~2001-09-28 12:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-28 12:44 Tom Tromey
2001-09-28 12:50 ` Daniel Jacobowitz [this message]

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=20010928155059.A17925@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb@sources.redhat.com \
    --cc=tromey@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