Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
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	[thread overview]
Message-ID: <1265631909-2821-1-git-send-email-brobecker@adacore.com> (raw)

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


             reply	other threads:[~2010-02-08 12:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-08 12:25 Joel Brobecker [this message]
2010-02-08 12:48 ` Mark Kettenis
2010-02-09 12:36   ` Joel Brobecker

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=1265631909-2821-1-git-send-email-brobecker@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    /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