From: Elena Zannoni <ezannoni@redhat.com>
To: Andreas Jaeger <aj@suse.de>
Cc: Andrew Cagney <ac131313@redhat.com>, gdb@sources.redhat.com
Subject: Re: GDB 6 branch, 21st June?
Date: Mon, 16 Jun 2003 13:52:00 -0000 [thread overview]
Message-ID: <16109.52534.183379.725367@localhost.redhat.com> (raw)
In-Reply-To: <ho3ciamb1a.fsf@byrd.suse.de>
Andreas Jaeger writes:
> Daniel Jacobowitz <drow@mvista.com> writes:
>
> > On Mon, Jun 16, 2003 at 08:39:20AM -0400, Andrew Cagney wrote:
> >> >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.
> >
> > i386-linux is down at around ten failures. Alpha's a bit higher,
>
> Ten failures sounds fine!
>
> > sparc's really rotten (thousands).
>
> I hope that even if we branch on the 21st, we have the possibility to
> get fixes for those failures on x86_64 into the branch? Unfortunatly
> Michal is on vacation until the 28th and cannot do anything himself -
> and I'm also occupied :-(
>
> Andreas
> --
> Andreas Jaeger
> SuSE Labs aj@suse.de
> private aj@arthur.inka.de
> http://www.suse.de/~aj
Usually we allow for a period of bugfixes/stabilization on the branch.
Here are my results on RHL9:
TODAY:
=== gdb Summary ===
# of expected passes 8970
# of unexpected failures 98
# of unexpected successes 4
# of expected failures 46
# of known failures 22
# of unresolved testcases 3
# of unsupported tests 1
while on 6-6-2003 I was getting a few less failures:
=== gdb Summary ===
# of expected passes 8868
# of unexpected failures 87
# of unexpected successes 4
# of expected failures 46
# of known failures 21
# of unresolved testcases 3
# of unsupported tests 1
here are the regressions/differences:
+FAIL: gdb.base/break.exp: until 79
+FAIL: gdb.base/break.exp: break on default location, 2nd time
+FAIL: gdb.base/break.exp: break on default location, 3rd time
+FAIL: gdb.base/break.exp: break on default location, 4th time
+Running /home/ezannoni/gdb-sources/src/gdb/testsuite/gdb.base/fileio.exp ...
+FAIL: gdb.base/fileio.exp: Renaming a directory to a non-empty directory returns ENOTEMPTY or EEXIST
Running /home/ezannoni/gdb-sources/src/gdb/testsuite/gdb.base/store.exp ...
-FAIL: gdb.base/store.exp: next field 1
-FAIL: gdb.base/store.exp: next field 2
-FAIL: gdb.base/store.exp: next field 3
-FAIL: gdb.base/store.exp: next field 4
+FAIL: gdb.base/store.exp: up print old r - char
+FAIL: gdb.base/store.exp: up print old r - short
+FAIL: gdb.base/store.exp: up print old r - int
+FAIL: gdb.base/store.exp: up print old r - long
+FAIL: gdb.base/store.exp: up print old r - longest
+FAIL: gdb.base/store.exp: up print old r - float
+FAIL: gdb.base/store.exp: up print old r - double
+FAIL: gdb.base/store.exp: up print old r - doublest
+FAIL: gdb.threads/linux-dp.exp: philosopher is distinct: 3
+FAIL: gdb.threads/linux-dp.exp: philosopher is distinct: 7
next prev parent reply other threads:[~2003-06-16 13:52 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
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 [this message]
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=16109.52534.183379.725367@localhost.redhat.com \
--to=ezannoni@redhat.com \
--cc=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