public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
* [committed][gdb/testsuite] Fix duplicate test-names in gdb.pascal
@ 2020-05-12  8:37 Tom de Vries
  0 siblings, 0 replies; only message in thread
From: Tom de Vries @ 2020-05-12  8:37 UTC (permalink / raw)
  To: gdb-patches

Hi,

In gdb.pascal we have these duplicates:
...
DUPLICATE: gdb.pascal/gdb11492.exp: next
DUPLICATE: gdb.pascal/gdb11492.exp: print char_array
...

Fix these by using with_test_prefix.

Tested on x86_64-linux.

Committed to trunk.

Thanks,
- Tom

[gdb/testsuite] Fix duplicate test-names in gdb.pascal

gdb/testsuite/ChangeLog:

2020-05-12  Tom de Vries  <tdevries@suse.de>

	* gdb.pascal/gdb11492.exp: Use with_test_prefix.

---
 gdb/testsuite/gdb.pascal/gdb11492.exp | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/gdb/testsuite/gdb.pascal/gdb11492.exp b/gdb/testsuite/gdb.pascal/gdb11492.exp
index a5a922ea91..fae6cd218f 100644
--- a/gdb/testsuite/gdb.pascal/gdb11492.exp
+++ b/gdb/testsuite/gdb.pascal/gdb11492.exp
@@ -46,7 +46,11 @@ gdb_test "print /d char_array" { = \{50, 51, 52, 53, 54, 55, 56, 57\}}
 gdb_test "print /x char_array" { = \{0x32, 0x33, 0x34, 0x35, 0x36, 0x37, 0x38, 0x39\}}
 # Use next two times to avoid GPC line numbering problem
 gdb_test "next" ""
-gdb_test "next" ""
-gdb_test "print char_array" " = '2345X789'"
+with_test_prefix "second" {
+    gdb_test "next" ""
+}
+with_test_prefix "after assignment" {
+    gdb_test "print char_array" " = '2345X789'"
+}
 gdb_exit
 

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2020-05-12  8:37 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-05-12  8:37 [committed][gdb/testsuite] Fix duplicate test-names in gdb.pascal Tom de Vries

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).