public inbox for gdb-cvs@sourceware.org help / color / mirror / Atom feed
From: Andrew Burgess <aburgess@sourceware.org> To: gdb-cvs@sourceware.org Subject: [binutils-gdb] gdb/testsuite: rename test source file to match test script Date: Wed, 25 Jan 2023 10:13:07 +0000 (GMT) [thread overview] Message-ID: <20230125101307.C5F853858C83@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=db8861ec34ad89f2c54ae8d51b353f0fedac3a3f commit db8861ec34ad89f2c54ae8d51b353f0fedac3a3f Author: Andrew Burgess <aburgess@redhat.com> Date: Thu Jan 12 13:24:40 2023 +0000 gdb/testsuite: rename test source file to match test script 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 to cpcompletion.cc to match the test script, this is more inline with how we name source files these days. Diff: --- gdb/testsuite/gdb.cp/{pr9594.cc => cpcompletion.cc} | 0 gdb/testsuite/gdb.cp/cpcompletion.exp | 2 +- 2 files changed, 1 insertion(+), 1 deletion(-) 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 d69aac6f79f..8c5c90b9357 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} { require allow_cplus_tests -standard_testfile pr9594.cc +standard_testfile .cc if {[prepare_for_testing "failed to prepare" $testfile $srcfile {debug c++}]} { return -1
reply other threads:[~2023-01-25 10:13 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=20230125101307.C5F853858C83@sourceware.org \ --to=aburgess@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: linkBe 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).