This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
[RFA/testsuite] Reduce the default test timeout to 30 seconds for Unix.
- From: Joel Brobecker <brobecker at adacore dot com>
- To: gdb-patches at sourceware dot org
- Date: Mon, 8 Feb 2010 16:25:09 +0400
- Subject: [RFA/testsuite] Reduce the default test timeout to 30 seconds for Unix.
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