This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
[commit] increase timeout for "maint print statistics" test
- From: dje at google dot com (Doug Evans)
- To: gdb-patches at sourceware dot org
- Date: Mon, 15 Nov 2010 09:20:18 -0800 (PST)
- Subject: [commit] increase timeout for "maint print statistics" test
Hi.
fyi, I checked this in.
I happened to see a timeout on a linux machine I was testing on
so I just increased the timeout for all targets.
Plus the test wasn't restoring the timeout afterwards.
2010-11-15 Doug Evans <dje@google.com>
* gdb.base/maint.exp (maint print statistics): Increase timeout for
all targets. Restore old timeout afterwards.
Index: gdb.base/maint.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.base/maint.exp,v
retrieving revision 1.49
diff -u -p -r1.49 maint.exp
--- gdb.base/maint.exp 9 Nov 2010 04:44:17 -0000 1.49
+++ gdb.base/maint.exp 15 Nov 2010 17:14:06 -0000
@@ -143,11 +143,10 @@ gdb_test "maint demangle main" "Can't de
# The timeout value is raised, because printing all the symbols and
# statistical information about Cygwin and Windows libraries takes a lot
-# of time.
-if [istarget "*-*-cygwin*"] {
- set oldtimeout $timeout
- set timeout [expr $timeout + 500]
-}
+# of time. This has been noticed on some linux systems too, so just raise
+# the timeout globally.
+set oldtimeout $timeout
+set timeout [expr $timeout + 500]
send_gdb "maint print statistics\n"
gdb_expect {
@@ -163,6 +162,8 @@ gdb_expect {
timeout { fail "(timeout) maint print statistics" }
}
+set timeout $oldtimeout
+
# There aren't any ...
gdb_test_no_output "maint print dummy-frames"