testsuite: Fix timeout issues during print of vla-arrays.

Printing and resolving of dynamic array's causes sporadic timeout issues on loaded systems.

2016-03-02  Bernhard Heckel  <bernhard.heckel@intel.com>

gdb/testsuite/Changelog:

     * gdb.fortran/vla-history.exp: Lookup array elements and printing exceeds timeout.

diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog
index cf69cce6044dc623f1338ae2c0c8c137e971eae3..889706f4510c714b325965489100e882d4a4bcc2 100644 (file)
--- a/gdb/testsuite/ChangeLog
+++ b/gdb/testsuite/ChangeLog
@@ -1,3 +1,7 @@
+2016-03-02  Bernhard Heckel  <bernhard.heckel@intel.com>
+
+       * gdb.fortran/vla-history.exp: Lookup array elements and printing exceeds timeout.
+
 2016-03-02  Bernhard Heckel  <bernhard.heckel@intel.com>
 
        * gdb.cp/vla-cxx.cc: Insert dummy assignment as anchor for an breakpoint.

diff --git a/gdb/testsuite/gdb.fortran/vla-history.exp b/gdb/testsuite/gdb.fortran/vla-history.exp
index 1478e6befc61da6a9627dab2fb5fbef2515055f3..bb2f84b78f5a344af2867a25dced6b07da2a4f0f 100644 (file)
--- a/gdb/testsuite/gdb.fortran/vla-history.exp
+++ b/gdb/testsuite/gdb.fortran/vla-history.exp
@@ -35,14 +35,18 @@ gdb_continue_to_breakpoint "vla2-allocated"
 
 gdb_breakpoint [gdb_get_line_number "vla1-filled"]
 gdb_continue_to_breakpoint "vla1-filled"
-gdb_test "print vla1" \
-  " = \\( *\\( *\\( *1311, *1311, *1311,\[()1311, .\]*\\)" \
-  "print vla1 filled"
+with_timeout_factor 2 {
+    gdb_test "print vla1" \
+      " = \\( *\\( *\\( *1311, *1311, *1311,\[()1311, .\]*\\)" \
+      "print vla1 filled"
+}
 
 # Try to access history values for full vla prints.
 gdb_test "print \$1" " = <not allocated>" "print \$1"
-gdb_test "print \$2" \
-  " = \\( *\\( *\\( *1311, *1311, *1311,\[()1311, .\]*\\)" "print \$2"
+with_timeout_factor 2 {
+    gdb_test "print \$2" \
+      " = \\( *\\( *\\( *1311, *1311, *1311,\[()1311, .\]*\\)" "print \$4"
+}
 
 gdb_breakpoint [gdb_get_line_number "vla2-filled"]
 gdb_continue_to_breakpoint "vla2-filled"