From: Jan Vrany <jan.vrany@labware.com>
To: gdb-patches@sourceware.org
Cc: Jan Vrany <jan.vrany@labware.com>
Subject: [PATCH] gdb/testsuite: increase timeout relatively to current one in huge.exp
Date: Wed, 10 Dec 2025 13:55:30 +0000 [thread overview]
Message-ID: <20251210135530.352680-1-jan.vrany@labware.com> (raw)
I occasionally run GDB testsuite on sluggish targets that need higher
timeout. The usual remedy I use is to set timeout to higher value in
site.exp.
This does not help with gdb.fortran/huge.exp, gdb.base/huge.exp and
gdb.ada/huge.exp, which set the timeout to fixed value of 30,
regardless of whether the timeout has been increased or not, causing
them to fail on some of my machines.
This commit fixes the problem by increasing the timeout relatively to
a multiple of current timeout in all three testcases.
---
gdb/testsuite/gdb.ada/huge.exp | 2 +-
gdb/testsuite/gdb.base/huge.exp | 2 +-
gdb/testsuite/gdb.fortran/huge.exp | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/gdb/testsuite/gdb.ada/huge.exp b/gdb/testsuite/gdb.ada/huge.exp
index 7bf70037f38..d0fc12025f7 100644
--- a/gdb/testsuite/gdb.ada/huge.exp
+++ b/gdb/testsuite/gdb.ada/huge.exp
@@ -52,7 +52,7 @@ foreach_with_prefix varname {Arr Packed_Arr} {
clean_restart ${testfile}
save_vars { timeout } {
- set timeout 30
+ set timeout [expr {$timeout * 3}]
if {![runto "foo"]} {
return
diff --git a/gdb/testsuite/gdb.base/huge.exp b/gdb/testsuite/gdb.base/huge.exp
index 4d164661608..cd4d8e36621 100644
--- a/gdb/testsuite/gdb.base/huge.exp
+++ b/gdb/testsuite/gdb.base/huge.exp
@@ -45,7 +45,7 @@ require {expr {$compilation_succeeded}}
clean_restart $testfile
save_vars { timeout } {
- set timeout 30
+ set timeout [expr {$timeout * 3}]
if {![runto_main]} {
return -1
diff --git a/gdb/testsuite/gdb.fortran/huge.exp b/gdb/testsuite/gdb.fortran/huge.exp
index 03ebdaac4bd..48e2ba4da0d 100644
--- a/gdb/testsuite/gdb.fortran/huge.exp
+++ b/gdb/testsuite/gdb.fortran/huge.exp
@@ -52,7 +52,7 @@ require {expr {$compilation_succeeded}}
clean_restart ${::testfile}
save_vars { timeout } {
- set timeout 30
+ set timeout [expr {$timeout * 3}]
if {![fortran_runto_main]} {
return -1
--
2.51.0
next reply other threads:[~2025-12-10 13:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-10 13:55 Jan Vrany [this message]
2025-12-10 16:29 ` Tom Tromey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20251210135530.352680-1-jan.vrany@labware.com \
--to=jan.vrany@labware.com \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox