From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7697 invoked by alias); 11 Mar 2010 00:11:36 -0000 Received: (qmail 7689 invoked by uid 22791); 11 Mar 2010 00:11:35 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from smtp-outbound-1.vmware.com (HELO smtp-outbound-1.vmware.com) (65.115.85.69) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 11 Mar 2010 00:11:30 +0000 Received: from mailhost3.vmware.com (mailhost3.vmware.com [10.16.27.45]) by smtp-outbound-1.vmware.com (Postfix) with ESMTP id 5361B1303D; Wed, 10 Mar 2010 16:11:27 -0800 (PST) Received: from [10.20.125.19] (unknown [10.20.125.19]) by mailhost3.vmware.com (Postfix) with ESMTP id 42830CD934; Wed, 10 Mar 2010 16:11:27 -0800 (PST) Message-ID: <4B98352E.4020603@vmware.com> Date: Thu, 11 Mar 2010 00:11:00 -0000 From: Michael Snyder User-Agent: Thunderbird 2.0.0.22 (X11/20090609) MIME-Version: 1.0 To: Doug Evans CC: "gdb-patches@sourceware.org" Subject: Re: [RFA] lengthen timeouts in gdb.base/checkpoint.exp References: <20100310235324.7B3288439C@ruffy.mtv.corp.google.com> In-Reply-To: <20100310235324.7B3288439C@ruffy.mtv.corp.google.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes 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: 2010-03/txt/msg00407.txt.bz2 Doug Evans wrote: > Hi. > > I'm seeing timeout failures in gdb.base/checkpoint.exp > on the 7.1 branch. > > Running ../../../../src/gdb/testsuite/gdb.base/checkpoint.exp ... > FAIL: gdb.base/checkpoint.exp: break2 with many checkpoints (timeout) > FAIL: gdb.base/checkpoint.exp: info checkpoints with at least 600 checkpoints (timeout) > FAIL: gdb.base/checkpoint.exp: kill all one (timeout) > > Ok to apply to trunk and 7.1 branch? > > I went with adding a number to the existing timeout value because > I didn't want to make any assumptions on what the existing timeout > value was (I can imagine wanting to globally increase the timeout > to some value when testing a slow serial target). > I cut-n-pasted the means to save/restore timeout from watchpoint.exp. > > 2010-03-10 Doug Evans > > * gdb.base/checkpoint.exp: Fix comment. > Lengthen timeout while doing >600 checkpoints test. > Rename duplicate "kill all one" test to keep test names unique. I'm ok with the timeout part. Are you really changing the number of checkpoints, or was the comment already obsolete? > Index: checkpoint.exp > =================================================================== > RCS file: /cvs/src/src/gdb/testsuite/gdb.base/checkpoint.exp,v > retrieving revision 1.11 > diff -u -p -r1.11 checkpoint.exp > --- checkpoint.exp 1 Jan 2010 07:32:00 -0000 1.11 > +++ checkpoint.exp 10 Mar 2010 23:46:20 -0000 > @@ -328,7 +328,7 @@ gdb_test "restart 9" "Not found.*" "no m > gdb_test "restart 10" "Not found.*" "no more checkpoint 10" > > # > -# Now let's try setting a large number of checkpoints (>1000) > +# Now let's try setting a large number of checkpoints (>600) > # > > gdb_exit > @@ -352,6 +352,10 @@ gdb_expect { > timeout { fail "(timeout) set checkpoint breakpoint" } > } > > +set prev_timeout $timeout > +set timeout [expr $timeout + 120] > +verbose "Timeout now $timeout sec." > + > gdb_breakpoint $break2_loc > gdb_test "continue" "breakpoint 2.*" "break2 with many checkpoints" > > @@ -375,9 +379,13 @@ gdb_test_multiple "info checkpoints" $ms > # OK, kill 'em all... > # > > -gdb_test "kill" "" "kill all one" \ > +gdb_test "kill" "" "kill all one with many checkpoints" \ > "Kill the program being debugged.*y or n. $" "y" > > +# Restore old timeout > +set timeout $prev_timeout > +verbose "Timeout now $timeout sec." > + > # > # Finished: cleanup > #