From: Tom Tromey <tromey@redhat.com>
To: gdb-patches@sourceware.org
Subject: FYI: fix test name in gdb-index.exp
Date: Wed, 28 Aug 2013 14:20:00 -0000 [thread overview]
Message-ID: <87vc2px5g3.fsf@fleche.redhat.com> (raw)
I'm checking this in.
The new gdb-index.exp test included a directory name in a test name.
This lead to spurious failures for me, because I ran the baseline tests
in a different directory.
Tom
2013-08-28 Tom Tromey <tromey@redhat.com>
* gdb.dwarf2/gdb-index.exp (add_gdb_index): Use explicit test name
when saving index.
Index: gdb.dwarf2/gdb-index.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.dwarf2/gdb-index.exp,v
retrieving revision 1.1
diff -u -r1.1 gdb-index.exp
--- gdb.dwarf2/gdb-index.exp 26 Aug 2013 18:43:40 -0000 1.1
+++ gdb.dwarf2/gdb-index.exp 28 Aug 2013 14:17:05 -0000
@@ -36,7 +36,8 @@
set index_file ${program}.gdb-index
verbose -log "index_file: ${index_file}"
remote_file host delete ${index_file}
- gdb_test_no_output "save gdb-index [file dirname ${index_file}]"
+ gdb_test_no_output "save gdb-index [file dirname ${index_file}]" \
+ "save gdb-index for file [file tail ${program}]"
# No point in continuing if generating the index failed.
# N.B.: There are times when gdb won't create an index, and it's not a
next reply other threads:[~2013-08-28 14:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-28 14:20 Tom Tromey [this message]
2013-08-28 14:55 ` Doug Evans
2013-08-28 15:58 ` Tom Tromey
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=87vc2px5g3.fsf@fleche.redhat.com \
--to=tromey@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