From de1c2c52237dd3e8d94df7b4a304ac9df75c8cf3 Mon Sep 17 00:00:00 2001 From: Pedro Alves Date: Fri, 7 Aug 2015 00:04:48 +0100 Subject: [PATCH] Bump timeouts for a couple gdb.reverse/*-precsave.exp tests The buildbot shows that PPC64 and x86_64 builders, both native and extended-remote gdbserver frequently timeout these tests. until-precsave.exp times out on my x86_64 occasionally as well. Inspecting the logs, we see that if we waited some more, the tests would pass. Simply bump until-precsave.exp timeouts further, and apply the same treatment to step-precsave.exp. gdb/testsuite/ChangeLog: 2015-08-06 Pedro Alves * gdb.reverse/step-precsave.exp: Use with_timeout_factor to increase timeout. * gdb.reverse/until-precsave.exp: Bump timeouts. --- gdb/testsuite/ChangeLog | 6 ++++++ gdb/testsuite/gdb.reverse/step-precsave.exp | 15 +++++++++++---- gdb/testsuite/gdb.reverse/until-precsave.exp | 4 ++-- 3 files changed, 19 insertions(+), 6 deletions(-) diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog index e4be76e..bf845a4 100644 --- a/gdb/testsuite/ChangeLog +++ b/gdb/testsuite/ChangeLog @@ -1,3 +1,9 @@ +2015-08-06 Pedro Alves + + * gdb.reverse/step-precsave.exp: Use with_timeout_factor to + increase timeout. + * gdb.reverse/until-precsave.exp: Bump timeouts. + 2015-08-06 Pedro Alves * gdb.base/valgrind-infcall.exp: Issue a "disconnect". diff --git a/gdb/testsuite/gdb.reverse/step-precsave.exp b/gdb/testsuite/gdb.reverse/step-precsave.exp index 5b1b416..f2a5299 100644 --- a/gdb/testsuite/gdb.reverse/step-precsave.exp +++ b/gdb/testsuite/gdb.reverse/step-precsave.exp @@ -44,11 +44,18 @@ gdb_test "break $end_of_main" \ "Breakpoint $decimal at .*$srcfile, line $end_of_main\." \ "BP at end of main" -gdb_test "continue" "Breakpoint .* end of main .*" "run to end of main" +# This can take awhile. +with_timeout_factor 20 { + gdb_test "continue" "Breakpoint .* end of main .*" "run to end of main" +} + +# So can this, against gdbserver, for example. -gdb_test "record save $precsave" \ - "Saved core file $precsave with execution log\." \ - "save process recfile" +with_timeout_factor 10 { + gdb_test "record save $precsave" \ + "Saved core file $precsave with execution log\." \ + "save process recfile" +} gdb_test "kill" "" "Kill process, prepare to debug log file" \ "Kill the program being debugged\\? \\(y or n\\) " "y" diff --git a/gdb/testsuite/gdb.reverse/until-precsave.exp b/gdb/testsuite/gdb.reverse/until-precsave.exp index 640839f..f0e9d1d 100644 --- a/gdb/testsuite/gdb.reverse/until-precsave.exp +++ b/gdb/testsuite/gdb.reverse/until-precsave.exp @@ -49,13 +49,13 @@ gdb_test "break $end_of_main" \ "BP at end of main" # This can take awhile. -with_timeout_factor 15 { +with_timeout_factor 20 { gdb_test "continue" "Breakpoint .* set breakpoint 10a here .*" "run to end of main" } # So can this, against gdbserver, for example. -with_timeout_factor 3 { +with_timeout_factor 10 { gdb_test "record save $precsave" \ "Saved core file $precsave with execution log\." \ "save process recfile" -- 2.7.4