From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: nickrob@snap.net.nz, gdb@sourceware.org
Subject: Re: [ANNOUNCEMENT] GDB 6.8 release process created!
Date: Sun, 02 Mar 2008 04:24:00 -0000 [thread overview]
Message-ID: <u1w6tkb3p.fsf@gnu.org> (raw)
In-Reply-To: <20080302035912.GA8955@caradoc.them.org> (message from Daniel Jacobowitz on Sat, 1 Mar 2008 22:59:12 -0500)
> Date: Sat, 1 Mar 2008 22:59:12 -0500
> From: Daniel Jacobowitz <drow@false.org>
> Cc: Eli Zaretskii <eliz@gnu.org>, gdb@sourceware.org
>
> On Sun, Mar 02, 2008 at 11:20:45AM +1300, Nick Roberts wrote:
> > That seems like a lot of failures.
>
> Mid-seventies is about typical for my runs. For instance most of the
> Ada tests blow up with current FSF gnat (Joel knows about this, the
> AdaCore sources work better). GPC, if you have it installed, fails a
> bunch of Pascal tests.
I have neither Gnat nor GPC on that machine, and the respective
failures are not in the test logfiles.
> > FAIL: gdb.base/annota1.exp: continue to printf
> > FAIL: gdb.base/annota1.exp: send SIGUSR1
> > FAIL: gdb.base/annota1.exp: signal sent
> > FAIL: gdb.cp/annota2.exp: continue to exit
> > FAIL: gdb.cp/annota2.exp: watch triggered on a.x
>
> I fixed these in HEAD right after I was informed of them. I don't
> think either the patch causing them or fixing them has been moved to
> the branch.
I don't see these in the logs, FWIW.
next prev parent reply other threads:[~2008-03-02 4:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-29 18:55 Joel Brobecker
2008-02-29 22:25 ` Thiago Jung Bauermann
2008-03-01 0:20 ` Joel Brobecker
2008-03-01 1:16 ` Daniel Jacobowitz
2008-03-03 17:30 ` Thiago Jung Bauermann
2008-03-01 9:47 ` Eli Zaretskii
2008-03-01 22:21 ` Nick Roberts
2008-03-02 3:59 ` Daniel Jacobowitz
2008-03-02 4:24 ` Eli Zaretskii [this message]
2008-03-02 4:22 ` Eli Zaretskii
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=u1w6tkb3p.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=drow@false.org \
--cc=gdb@sourceware.org \
--cc=nickrob@snap.net.nz \
/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