This is the mail archive of the mailing list for the GDB project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[commit] testsuite: Extend timeout: gdb.reverse/until-precsave.exp: run to end of main


there has been checked in a similar patch:
	[patch] i387-env-reverse.exp: Extend timeout of "record to end of main" test.

Seeing a similar problem during various configurations for:
	-PASS: gdb.reverse/until-precsave.exp: run to end of main
	+FAIL: gdb.reverse/until-precsave.exp: run to end of main (timeout)

Checked in.


--- src/gdb/testsuite/ChangeLog	2011/12/08 15:31:20	1.2972
+++ src/gdb/testsuite/ChangeLog	2011/12/09 17:36:01	1.2973
@@ -1,3 +1,8 @@
+2011-12-09  Jan Kratochvil  <>
+	* gdb.reverse/until-precsave.exp (run to end of main) Extend the
+	timeout.
 2011-12-08  Tom Tromey  <>
 	* gdb.cp/ovsrch.exp (test_class): Correctly use "a_param" in
--- src/gdb/testsuite/gdb.reverse/until-precsave.exp	2011/11/08 08:23:48	1.5
+++ src/gdb/testsuite/gdb.reverse/until-precsave.exp	2011/12/09 17:36:02	1.6
@@ -48,7 +48,11 @@
     "Breakpoint $decimal at .*/$srcfile, line $end_of_main\." \
     "BP at end of main"
+# This can take awhile.
+set oldtimeout $timeout
+set timeout [expr $oldtimeout + 120]
 gdb_test "continue" "Breakpoint .* set breakpoint 10a here .*" "run to end of main"
+set timeout $oldtimeout
 gdb_test "record save until.precsave" \
     "Saved core file until.precsave with execution log\."  \

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]