From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [pushed] [gdb/testsuite] Fix DUPLICATE in gdb.arch/ppc-fp.exp
Date: Thu, 17 Nov 2022 09:12:47 +0100 [thread overview]
Message-ID: <20221117081247.23366-1-tdevries@suse.de> (raw)
From: Tom de Vries <tdevries@jostaberry-8.arch.suse.de>
I noticed:
...
DUPLICATE: gdb.arch/ppc-fp.exp: next
...
Fix this by adding unique test names.
Tested on powerpc64le-linux.
---
gdb/testsuite/gdb.arch/ppc-fp.exp | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/gdb/testsuite/gdb.arch/ppc-fp.exp b/gdb/testsuite/gdb.arch/ppc-fp.exp
index bf1a1c59082..bd22d7c489e 100644
--- a/gdb/testsuite/gdb.arch/ppc-fp.exp
+++ b/gdb/testsuite/gdb.arch/ppc-fp.exp
@@ -61,7 +61,7 @@ gdb_test_multiple "print \$fpscr" "FPSCR exists" {
}
# Step over invalid operation.
-gdb_test "next" "" ""
+gdb_test "next" "" "next over invalid operation"
# Verify that the following bits are set (See Power ISA for details):
#
@@ -75,7 +75,7 @@ gdb_test "print/t \$fpscr" " = 10100000001000010001000000000000" "FPSCR for inva
gdb_continue_to_breakpoint "go to division by zero"
# Step over division by zero.
-gdb_test "next" "" ""
+gdb_test "next" "" "next over division by zero"
# Verify that the following bits are set (See Power ISA for details):
#
base-commit: d5b9201744fa1dcfcde2e06140efe28819aaef25
--
2.35.3
reply other threads:[~2022-11-17 8:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20221117081247.23366-1-tdevries@suse.de \
--to=tdevries@suse.de \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).