public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
From: Lancelot SIX <lsix@sourceware.org>
To: gdb-cvs@sourceware.org
Subject: [binutils-gdb] gdb/testsuite: Remove duplicates from gdb.base/pretty-array.exp
Date: Fri,  7 Jan 2022 22:45:51 +0000 (GMT)	[thread overview]
Message-ID: <20220107224551.CBD923857C69@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=22dafa45d306e4086615d1269e0a3c504e284da5

commit 22dafa45d306e4086615d1269e0a3c504e284da5
Author: Lancelot SIX <lsix@lancelotsix.com>
Date:   Sun Nov 21 00:29:01 2021 +0000

    gdb/testsuite: Remove duplicates from gdb.base/pretty-array.exp
    
    When I run the testsuite, I have:
    
        Running .../gdb/testsuite/gdb.base/pretty-array.exp ...
        DUPLICATE: gdb.base/pretty-array.exp: print nums
        DUPLICATE: gdb.base/pretty-array.exp: print nums
    
    Fix by giving a name to the test cases.
    
    Tested on x86_64-linux.

Diff:
---
 gdb/testsuite/gdb.base/pretty-array.exp | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/gdb/testsuite/gdb.base/pretty-array.exp b/gdb/testsuite/gdb.base/pretty-array.exp
index 3ababed4bc4..8f7bb4de640 100644
--- a/gdb/testsuite/gdb.base/pretty-array.exp
+++ b/gdb/testsuite/gdb.base/pretty-array.exp
@@ -44,7 +44,8 @@ gdb_test "print nums" \
 	 "    22," \
 	 "    23" \
 	 "  }" \
-	 "}" ]
+	 "}" ] \
+    "print nums with print array on"
 
 gdb_test_no_output "set print array-indexes on"
 
@@ -61,4 +62,5 @@ gdb_test "print nums" \
 	 "    \\\[1\\\] = 22," \
 	 "    \\\[2\\\] = 23" \
 	 "  }" \
-	 "}" ]
+	 "}" ] \
+    "print nums with print array on, print array-indexes on"


                 reply	other threads:[~2022-01-07 22:45 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=20220107224551.CBD923857C69@sourceware.org \
    --to=lsix@sourceware.org \
    --cc=gdb-cvs@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).