From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13842 invoked by alias); 8 Feb 2010 12:25:28 -0000 Received: (qmail 13830 invoked by uid 22791); 8 Feb 2010 12:25:27 -0000 X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 08 Feb 2010 12:25:24 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 80DC92BAB91 for ; Mon, 8 Feb 2010 07:25:22 -0500 (EST) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id QleHjcmttu1o for ; Mon, 8 Feb 2010 07:25:22 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id DBC2B2BAB5F for ; Mon, 8 Feb 2010 07:25:21 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id 74B18F59A2; Mon, 8 Feb 2010 16:25:10 +0400 (RET) From: Joel Brobecker To: gdb-patches@sourceware.org Subject: [RFA/testsuite] Reduce the default test timeout to 30 seconds for Unix. Date: Mon, 08 Feb 2010 12:25:00 -0000 Message-Id: <1265631909-2821-1-git-send-email-brobecker@adacore.com> 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-02/txt/msg00204.txt.bz2 Hello, This is something that I noticed while working on testcase timeouts... This patch reduces the timeout duration used for all "unix" native configurations from 60 seconds down to 30 seconds. Even under NFS and heavy loads, 60 seconds seems a bit excessive. This might not be very important if we manage to find a way to implement the idea of aborting a testcase as soon as the first timeout gets hit. But in the menatime, this reduces significantly the amount of time spend multi-timing out... (no idea on how to do that so far, though) In the few situations where 30 seconds, which is already 3 times the dejagnu default, is not enough, the user has the possibility of changing the timeout duration back to any value by definining gdb_test_timeout. gdb/testsuite/ChangeLog: * config/unix.exp (timeout): Change value to 30. Tested on x86_64-linux. No regression. Any objection? Thanks, -- Joel --- gdb/testsuite/config/unix.exp | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/gdb/testsuite/config/unix.exp b/gdb/testsuite/config/unix.exp index 711b461..c4ca444 100644 --- a/gdb/testsuite/config/unix.exp +++ b/gdb/testsuite/config/unix.exp @@ -20,7 +20,7 @@ # accepting whatever default dejagnu gives us (apparently 10 seconds). # When running the tests over NFS, under somewhat heavy load, 10 seconds # does not seem to be enough. Try starting with 60. -set timeout 60 +set timeout 30 verbose "Timeout is now $timeout seconds" 2 load_lib gdb.exp -- 1.6.3.3