public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
From: Tom Tromey <tromey@sourceware.org>
To: gdb-cvs@sourceware.org
Subject: [binutils-gdb] Remove path name from test
Date: Sun, 22 Jan 2023 21:28:28 +0000 (GMT)	[thread overview]
Message-ID: <20230122212828.4AF643858421@sourceware.org> (raw)

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

commit 2292e336c64bc365ceed12231a516c3f3068c869
Author: Tom Tromey <tom@tromey.com>
Date:   Sat Jan 21 14:59:16 2023 -0700

    Remove path name from test
    
    The test suite reports several path names in tests.  I couldn't find
    most of these, and I suspect they are false reports, but I did manage
    to locate one.  This one is probably harmless, as I think the path
    does not vary; but it's also easy to fix and suppress one warning.

Diff:
---
 gdb/testsuite/gdb.python/py-parameter.exp | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/gdb/testsuite/gdb.python/py-parameter.exp b/gdb/testsuite/gdb.python/py-parameter.exp
index 09a03083d03..c1f8a80c6b7 100644
--- a/gdb/testsuite/gdb.python/py-parameter.exp
+++ b/gdb/testsuite/gdb.python/py-parameter.exp
@@ -76,7 +76,8 @@ proc_with_prefix test_data_directory { } {
     set rel_path_to_output_dir \
 	[file join "." [string replace ${abs_path_to_output_dir} 0 \
 			    [string length ${abs_path_to_cwd}] ""]]
-    gdb_test_no_output "set data-directory ${rel_path_to_output_dir}"
+    gdb_test_no_output "set data-directory ${rel_path_to_output_dir}" \
+	"set data-directory to relative path"
 
     gdb_test "python print (gdb.parameter ('data-directory'))" \
 	${abs_path_to_output_dir} \

                 reply	other threads:[~2023-01-22 21:28 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=20230122212828.4AF643858421@sourceware.org \
    --to=tromey@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).