From: Andrew Burgess <andrew.burgess@embecosm.com>
To: gdb-patches@sourceware.org
Subject: [PUSHED] gdb/testsuite: resolve duplicate test names in gdb.guile/*.exp
Date: Wed, 19 May 2021 13:41:27 +0100 [thread overview]
Message-ID: <20210519124127.1598548-1-andrew.burgess@embecosm.com> (raw)
This commit:
commit ecf25064e87a3d2d59871b3ea7126fa0dee0001d
Date: Thu May 13 15:42:20 2021 +0100
gdb: fix pretty printing max depth behaviour
Introduced a couple of duplicate tests, this commit resolves them by
providing unique test names.
gdb/testsuite/ChangeLog:
* gdb.guile/scm-pretty-print.exp: Add test names to resolve
duplicate test names.
---
gdb/testsuite/ChangeLog | 5 +++++
gdb/testsuite/gdb.guile/scm-pretty-print.exp | 7 ++++---
2 files changed, 9 insertions(+), 3 deletions(-)
diff --git a/gdb/testsuite/gdb.guile/scm-pretty-print.exp b/gdb/testsuite/gdb.guile/scm-pretty-print.exp
index 7bd9d469ff6..00229efd806 100644
--- a/gdb/testsuite/gdb.guile/scm-pretty-print.exp
+++ b/gdb/testsuite/gdb.guile/scm-pretty-print.exp
@@ -90,10 +90,11 @@ proc run_lang_tests {exefile lang} {
}
gdb_test "print x" " = \"this is x\""
- gdb_test "print cstring" " = \"const string\""
-
+ gdb_test "print cstring" " = \"const string\"" \
+ "print cstring with max-depth unlimited"
gdb_test_no_output "set print max-depth 0"
- gdb_test "print cstring" " = \"const string\""
+ gdb_test "print cstring" " = \"const string\"" \
+ "print cstring with max-depth 0"
gdb_test_no_output "set print max-depth unlimited"
gdb_test "print estring" " = \"embedded x\\\\201\\\\202\\\\203\\\\204\""
--
2.25.4
reply other threads:[~2021-05-19 12:41 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=20210519124127.1598548-1-andrew.burgess@embecosm.com \
--to=andrew.burgess@embecosm.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).