[7/8] gdb.trace: Bump tspeed.exp timeout to 600 seconds.
Commit Message
It seems the 180 seconds timeout is quite tight on my z13 machine,
and causes failures when the machine is somewhat loaded.
gdb/testsuite/ChangeLog:
* gdb.trace/tspeed.exp: Bump the timeout to 600 seconds.
---
gdb/testsuite/ChangeLog | 4 ++++
gdb/testsuite/gdb.trace/tspeed.exp | 2 +-
2 files changed, 5 insertions(+), 1 deletion(-)
Comments
On Sun, Jan 24 2016, Marcin Kościelnicki wrote:
> It seems the 180 seconds timeout is quite tight on my z13 machine,
> and causes failures when the machine is somewhat loaded.
>
> gdb/testsuite/ChangeLog:
>
> * gdb.trace/tspeed.exp: Bump the timeout to 600 seconds.
> ---
[...]
> diff --git a/gdb/testsuite/gdb.trace/tspeed.exp b/gdb/testsuite/gdb.trace/tspeed.exp
> index e638839..204eda7 100644
> --- a/gdb/testsuite/gdb.trace/tspeed.exp
> +++ b/gdb/testsuite/gdb.trace/tspeed.exp
> @@ -27,7 +27,7 @@ if { [gdb_compile "$srcdir/$subdir/$srcfile" $binfile \
> }
>
> # Typically we need a little extra time for this test.
> -set timeout 180
> +set timeout 300
This doesn't match the ChangeLog entry and patch description ;-)
>
> set ws "\[\r\n\t \]+"
> set cr "\[\r\n\]+"
@@ -1,5 +1,9 @@
2016-01-24 Marcin Kościelnicki <koriakin@0x04.net>
+ * gdb.trace/tspeed.exp: Bump the timeout to 600 seconds.
+
+2016-01-24 Marcin Kościelnicki <koriakin@0x04.net>
+
* gdb.trace/ftrace.exp: Select $r2 as test register for s390.
* gdb.trace/mi-trace-frame-collected.exp: Expect 2 registers on s390.
* gdb.trace/trace-common.h (x86_trace_dummy): Add s390 fast tracepoint
@@ -27,7 +27,7 @@ if { [gdb_compile "$srcdir/$subdir/$srcfile" $binfile \
}
# Typically we need a little extra time for this test.
-set timeout 180
+set timeout 300
set ws "\[\r\n\t \]+"
set cr "\[\r\n\]+"