From: Tom de Vries <tdevries@suse.de>
To: Luis Machado <luis.machado@arm.com>, gdb-patches@sourceware.org
Cc: Carl Love <cel@us.ibm.com>, Ulrich Weigand <Ulrich.Weigand@de.ibm.com>
Subject: Re: [PATCH] [gdb/testsuite] Fix gdb.ada/float-bits.exp for powerpc64le
Date: Thu, 1 Dec 2022 15:40:34 +0100 [thread overview]
Message-ID: <a6d480ba-2877-08bd-2994-76f3be78973c@suse.de> (raw)
In-Reply-To: <0839ffa1-e99b-a6a5-ac01-d8e3fb5fdf1b@arm.com>
[-- Attachment #1: Type: text/plain, Size: 417 bytes --]
On 12/1/22 14:49, Luis Machado wrote:
> This change seems to be causing a timeout on aarch64-linux Ubuntu 22.04.
>
> FAIL: gdb.ada/float-bits.exp: maint print architecture (timeout)
>
> # of expected passes 12
> # of unexpected failures 1
>
> It is as if the listing of the architecture fields didn't have time to
> finish.
>
Can you see if this fixes things?
Thanks,
- Tom
[-- Attachment #2: 0001-gdb-testsuite-Fix-timeout-in-gdb.ada-float-bits.exp.patch --]
[-- Type: text/x-patch, Size: 1628 bytes --]
From a2c476bbc9fde2e661c035cb2c1e460da5bbee49 Mon Sep 17 00:00:00 2001
From: Tom de Vries <tdevries@suse.de>
Date: Thu, 1 Dec 2022 15:28:48 +0100
Subject: [PATCH] [gdb/testsuite] Fix timeout in gdb.ada/float-bits.exp
A timeout was reported:
...
FAIL: gdb.ada/float-bits.exp: maint print architecture (timeout)
...
after recent commit 32a5aa26256 ("[gdb/testsuite] Fix gdb.ada/float-bits.exp
for powerpc64le").
Fix this by rewriting the gdb_test_multiple to read line-by-line.
Tested on x86_64-linux.
---
gdb/testsuite/gdb.ada/float-bits.exp | 13 ++++++++++---
1 file changed, 10 insertions(+), 3 deletions(-)
diff --git a/gdb/testsuite/gdb.ada/float-bits.exp b/gdb/testsuite/gdb.ada/float-bits.exp
index 921fe36a4bd..dab16a60286 100644
--- a/gdb/testsuite/gdb.ada/float-bits.exp
+++ b/gdb/testsuite/gdb.ada/float-bits.exp
@@ -75,14 +75,21 @@ set gdb_long_double_size [float_size "16llf#0#" ]
# Get the used long double format.
set long_double_format ""
-gdb_test_multiple "maint print architecture" "" {
- -re "\r\ngdbarch_dump: long_double_format = (\[^\r\n\]*)" {
+set cmd "maint print architecture"
+gdb_test_multiple $cmd "" {
+ -re "^[string_to_regexp $cmd](?=\r\n)" {
+ exp_continue
+ }
+ -re "^\r\ngdbarch_dump: long_double_format = (\[^\r\n\]*)(?=\r\n)" {
set long_double_format $expect_out(1,string)
exp_continue
}
- -re -wrap "" {
+ -re "^\r\n$gdb_prompt $" {
pass $gdb_test_name
}
+ -re "^\r\n(\[^\r\n\]*)(?=\r\n)" {
+ exp_continue
+ }
}
# Set default values for 128-bit IEEE quad long doubles.
base-commit: 6ef35c04dffe685ece08212201c4c032baf8aa86
--
2.35.3
next prev parent reply other threads:[~2022-12-01 14:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 14:00 Tom de Vries
2022-11-30 14:51 ` Tom Tromey
2022-11-30 16:18 ` Carl Love
2022-12-01 13:49 ` Luis Machado
2022-12-01 14:40 ` Tom de Vries [this message]
2022-12-01 20:51 ` Luis Machado
2022-12-01 21:01 ` Luis Machado
2022-12-02 7:59 ` Tom de Vries
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=a6d480ba-2877-08bd-2994-76f3be78973c@suse.de \
--to=tdevries@suse.de \
--cc=Ulrich.Weigand@de.ibm.com \
--cc=cel@us.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=luis.machado@arm.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).