From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3552 invoked by alias); 2 Mar 2008 04:24:29 -0000 Received: (qmail 3188 invoked by uid 22791); 2 Mar 2008 04:24:27 -0000 X-Spam-Check-By: sourceware.org Received: from nitzan.inter.net.il (HELO nitzan.inter.net.il) (213.8.233.22) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sun, 02 Mar 2008 04:24:01 +0000 Received: from HOME-C4E4A596F7 (IGLD-84-228-167-98.inter.net.il [84.228.167.98]) by nitzan.inter.net.il (MOS 3.7.3a-GA) with ESMTP id JIW64284 (AUTH halo1); Sun, 2 Mar 2008 06:21:12 +0200 (IST) Date: Sun, 02 Mar 2008 04:24:00 -0000 Message-Id: From: Eli Zaretskii To: Daniel Jacobowitz CC: nickrob@snap.net.nz, gdb@sourceware.org In-reply-to: <20080302035912.GA8955@caradoc.them.org> (message from Daniel Jacobowitz on Sat, 1 Mar 2008 22:59:12 -0500) Subject: Re: [ANNOUNCEMENT] GDB 6.8 release process created! Reply-to: Eli Zaretskii References: <18377.54973.885633.998260@kahikatea.snap.net.nz> <20080302035912.GA8955@caradoc.them.org> X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2008-03/txt/msg00012.txt.bz2 > Date: Sat, 1 Mar 2008 22:59:12 -0500 > From: Daniel Jacobowitz > Cc: Eli Zaretskii , 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.