Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Elizabeth Chastain <mec@shout.net>
To: jjohnstn@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA: modernization of ia64-tdep.c with new frame model for gdb-6.0 branch
Date: Fri, 08 Aug 2003 17:49:00 -0000	[thread overview]
Message-ID: <200308081749.h78HnOGU016412@duracef.shout.net> (raw)

>         === gdb Summary ===
> 
> # of expected passes        5197
> # of unexpected failures    28
> # of unexpected successes    2
> # of expected failures        12
> # of known failures        1
> # of unresolved testcases    1
> # of unsupported tests        1

That is light on the # of expected passes.

For comparison, I am getting 9000 expected passes with gdb HEAD and gdb
gdb_6_0-branch on native i686-pc-linux-gnu.

Can you check your gdb.sum file and see if there are any
ERROR lines or WARNING lines in it?  Unfortunately, the summary does
not include counts for those.

Or it could be that ia64 doesn't run as many tests as i686.
But 3800 missing tests is a LOT of tests.

Michael C


             reply	other threads:[~2003-08-08 17:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-08 17:49 Michael Elizabeth Chastain [this message]
2003-08-08 18:57 ` J. Johnston
  -- strict thread matches above, loose matches on Subject: below --
2003-07-30 20:54 J. Johnston
2003-07-31 19:03 ` J. Johnston
2003-07-31 19:20   ` Daniel Jacobowitz
2003-07-31 21:39     ` J. Johnston
2003-08-08 17:32 ` J. Johnston
2003-08-22 21:46   ` Kevin Buettner
2003-08-25 18:12     ` J. Johnston
2003-08-25 18:41       ` Kevin Buettner
2003-08-25 23:29         ` J. Johnston

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=200308081749.h78HnOGU016412@duracef.shout.net \
    --to=mec@shout.net \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jjohnstn@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