From: Andrew Burgess <aburgess@redhat.com>
To: gdb-patches@sourceware.org
Cc: Andrew Burgess <aburgess@redhat.com>
Subject: [PATCH 2/2] gdb/testsuite: rename test source file to match test script
Date: Thu, 12 Jan 2023 19:08:11 +0000 [thread overview]
Message-ID: <cf53786dfd52ea3f372512b37f7b091f77601445.1673550414.git.aburgess@redhat.com> (raw)
In-Reply-To: <cover.1673550414.git.aburgess@redhat.com>
The previous commit touched the source file for the test script
gdb.cp/cpcompletion.exp. This source file is called pr9594.cc. The
source file is only used by the one test script.
This commit renames the source file cpcompletion.cc to match the test
script, this is more inline with how we name source files these days.
---
gdb/testsuite/gdb.cp/{pr9594.cc => cpcompletion.cc} | 0
gdb/testsuite/gdb.cp/cpcompletion.exp | 2 +-
2 files changed, 1 insertion(+), 1 deletion(-)
rename gdb/testsuite/gdb.cp/{pr9594.cc => cpcompletion.cc} (100%)
diff --git a/gdb/testsuite/gdb.cp/pr9594.cc b/gdb/testsuite/gdb.cp/cpcompletion.cc
similarity index 100%
rename from gdb/testsuite/gdb.cp/pr9594.cc
rename to gdb/testsuite/gdb.cp/cpcompletion.cc
diff --git a/gdb/testsuite/gdb.cp/cpcompletion.exp b/gdb/testsuite/gdb.cp/cpcompletion.exp
index 371e90cca7d..a3b09239f30 100644
--- a/gdb/testsuite/gdb.cp/cpcompletion.exp
+++ b/gdb/testsuite/gdb.cp/cpcompletion.exp
@@ -53,7 +53,7 @@ proc test_class_complete {class expr name matches} {
if { [skip_cplus_tests] } { continue }
-standard_testfile pr9594.cc
+standard_testfile .cc
if {[prepare_for_testing "failed to prepare" $testfile $srcfile {debug c++}]} {
return -1
--
2.25.4
next prev parent reply other threads:[~2023-01-12 19:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 19:08 [PATCH 0/2] Cleanup the gdb.cp/cpcompletion.exp test Andrew Burgess
2023-01-12 19:08 ` [PATCH 1/2] gdb/testsuite: use test_gdb_complete_unique more in C++ tests Andrew Burgess
2023-01-12 19:08 ` Andrew Burgess [this message]
2023-01-25 10:13 ` [PATCH 0/2] Cleanup the gdb.cp/cpcompletion.exp test Andrew Burgess
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=cf53786dfd52ea3f372512b37f7b091f77601445.1673550414.git.aburgess@redhat.com \
--to=aburgess@redhat.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).