From: Andrew Cagney <ac131313@redhat.com>
To: Andreas Jaeger <aj@suse.de>
Cc: gdb@sources.redhat.com
Subject: Re: GDB 6 branch, 21st June?
Date: Mon, 16 Jun 2003 12:39:00 -0000 [thread overview]
Message-ID: <3EEDBA78.2030609@redhat.com> (raw)
In-Reply-To: <hoptleqtzi.fsf@byrd.suse.de>
> Andrew Cagney <ac131313@redhat.com> writes:
>
>
>> Still scheduled for 21st, how is that looking?
>
>
> We currently have the following results from make check on
> x86_64-linux-gnu:
>
> === gdb Summary ===
>
> # of expected passes 8930
> # of unexpected failures 100
> # of unexpected successes 4
> # of expected failures 46
> # of known failures 23
> # of unresolved testcases 3
> # of untested testcases 6
> # of unsupported tests 1
> /usr/src/aj/build/gdb/gdb/testsuite/../../gdb/gdb version 2003-06-16-cvs -nx
>
>
> How does this look in comparison with other platforms?
Pretty much on par. break main, run, next definitly works.
Andrew
next prev parent reply other threads:[~2003-06-16 12:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-13 23:46 Andrew Cagney
2003-06-16 8:59 ` Andreas Jaeger
2003-06-16 12:39 ` Andrew Cagney [this message]
2003-06-16 12:51 ` Daniel Jacobowitz
2003-06-16 13:01 ` Andreas Jaeger
2003-06-16 13:48 ` Andrew Cagney
2003-06-16 13:52 ` Elena Zannoni
2003-06-16 17:44 ` David Carlton
2003-06-16 18:51 ` Elena Zannoni
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=3EEDBA78.2030609@redhat.com \
--to=ac131313@redhat.com \
--cc=aj@suse.de \
--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