From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9505 invoked by alias); 27 Mar 2008 13:40:12 -0000 Received: (qmail 9327 invoked by uid 22791); 27 Mar 2008 13:40:11 -0000 X-Spam-Check-By: sourceware.org Received: from zigzag.lvk.cs.msu.su (HELO zigzag.lvk.cs.msu.su) (158.250.17.23) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 27 Mar 2008 13:39:40 +0000 Received: from Debian-exim by zigzag.lvk.cs.msu.su with spam-scanned (Exim 4.63) (envelope-from ) id 1JesKM-0002LS-6h for gdb-patches@sources.redhat.com; Thu, 27 Mar 2008 16:39:37 +0300 Received: from localhost ([127.0.0.1] helo=ip6-localhost) by zigzag.lvk.cs.msu.su with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from ) id 1JesK9-0002LC-I2; Thu, 27 Mar 2008 16:39:21 +0300 From: Vladimir Prus To: Markus Deuling Subject: Re: FAILs on x86? Date: Thu, 27 Mar 2008 13:40:00 -0000 User-Agent: KMail/1.9.6 (enterprise 0.20070907.709405) Cc: gdb-patches@sources.redhat.com References: <47EB86DF.10803@de.ibm.com> <200803271554.49239.ghost@cs.msu.su> <47EBA113.2030904@de.ibm.com> In-Reply-To: <47EBA113.2030904@de.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200803271639.21190.ghost@cs.msu.su> Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2008-03/txt/msg00434.txt.bz2 On Thursday 27 March 2008 16:28:51 Markus Deuling wrote: > Vladimir Prus schrieb: > > On Thursday 27 March 2008 15:33:08 Markus Deuling wrote: > >> Vladimir Prus schrieb: > >>> Markus Deuling wrote: > >>> > >>>> Daniel Jacobowitz schrieb: > >>>>> On Thu, Mar 27, 2008 at 12:37:03PM +0100, Markus Deuling wrote: > >>>>>> Hi, > >>>>>> > >>>>>> I see lots of FAILs on x86. Anyone else seeing this? > >>>>> Not me. What's in gdb.log for a typical failure? > >>>>> > >>>> Nothing special, I think (I dont think its an environment problem). Just a lot of FAILs in > >>>> gdb.{base,cp,mi}. I posted a list of the FAILs that are new compared to a testrun some days ago > >>>> here: > >>>> > >>>> http://sourceware.org/ml/gdb-testers/2008-q1/msg00022.html > >>>> > >>>> As far as I see there were some commits to some areas where GDB test fails > >>>> now (gdb.cp, gdb.mi, dfp). If needed I can attach gdb.log > >>> When were the tests run? gdb.mi failures are supposed to be fixed now. > >>> > >>> - Volodya > >>> > >> Today, just an hour ago. I currently re-run tests for ppc and spu. > >> > > > > Strange. Does testsuite/Changelog have the following: > > > > 2008-03-26 Vladimir Prus > > > > * lib/mi-support.exp (mi_create_varobj_checked): New. > > (mi_list_varobj_children): Allow to check for a > > value. > > (mi_list_array_varobj_children): New. > > > > * gdb.mi/mi-var-child.exp: Use mi_create_varobj > > and mi_list_varobj_children, as opposed to hardcoding > > expected strings. > > * gdb.mi/gdb701.exp: Likewise. > > * gdb.mi/gdb792.exp: Likewise. > > * gdb.mi/mi-var-block.exp: Likewise. > > * gdb.mi/mi-var-cmd.exp: Likewise. > > * gdb.mi/mi-var-invalidate.exp: Likewise. > > * gdb.mi/mi2-var-block.exp: Likewise. > > * gdb.mi/mi2-var-child.exp: Likewise. > > * gdb.mi/mi2-var-cmd.exp: Likewise. > > * gdb.mi/mi2-var-display.exp: Likewise. > > > > ? > > > > - Volodya > > > > > > Yes, I test against current head. Then, I need gdb.log part for the first failure, namely this: FAIL: gdb.mi/gdb701.exp: create fooPtr - Volodya