From: Simon Marchi <simon.marchi@polymtl.ca>
To: Luis Machado <lgustavo@codesourcery.com>
Cc: Pedro Alves <palves@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 1/8] Fixup testcases outputting own name as a test name
Date: Fri, 25 Nov 2016 17:48:00 -0000 [thread overview]
Message-ID: <5cfc70b2ea19762c664d61f752c02a41@polymtl.ca> (raw)
In-Reply-To: <2b7ca30d-f563-dd11-7934-60505d261a24@codesourcery.com>
On 2016-11-25 12:37, Luis Machado wrote:
>> I think all these references to $binfile will put the full file
>> path on gdb.sum? I think you want $testfile instead.
>>
>> Thanks,
>> Pedro Alves
>>
>
> They will, which may make it easier to just build the files by hand
> with the output from the log file. But it has the potential to be a
> big path.
>
> I'm fine with either approach.
I think it's fine how you did in the patch. Most of the time, binfile
is based on testfile, so Pedro's suggestion would work. But sometimes,
we pass something else than binfile as the compilation destination (or
binfile was overrident), so we would have to remember to use something
else than testfile to build the error message, it seems easy to forget.
I think that consistently using the same expression as is passed to
gdb_compile's dest parameter is a good approach. Or maybe the error
should be handled in gdb_compile instead of in each individual test,
that would be even less error-prone.
Of course, that doesn't hold if the issue about having the full paths in
the test message is about the reproducibility (test names will have
different names depending on the path where you build gdb). But since
it's only for error test names, I don't know if that's a real problem.
next prev parent reply other threads:[~2016-11-25 17:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-25 17:09 [PATCH 0/8] Fix gdb's testsuite test names Luis Machado
2016-11-25 17:09 ` [PATCH 5/8] Fix test names starting with uppercase using gdb_test_multiple Luis Machado
2016-11-25 17:09 ` [PATCH 8/8] Fix test names starting with uppercase using multi-line gdb_test_multiple Luis Machado
2016-11-25 17:09 ` [PATCH 6/8] Fix test names starting with uppercase using multi-line gdb_test/mi_gdb_test Luis Machado
2016-11-25 17:09 ` [PATCH 4/8] Fix test names starting with uppercase using gdb_test_no_output Luis Machado
2016-11-25 17:09 ` [PATCH 3/8] Fix test names starting with uppercase using gdb_test on a single line Luis Machado
2016-11-25 17:09 ` [PATCH 1/8] Fixup testcases outputting own name as a test name Luis Machado
2016-11-25 17:28 ` Pedro Alves
2016-11-25 17:37 ` Luis Machado
2016-11-25 17:48 ` Simon Marchi [this message]
2016-11-25 17:53 ` Luis Machado
2016-11-25 17:55 ` Pedro Alves
2016-11-25 18:02 ` Simon Marchi
2016-11-25 18:26 ` Luis Machado
2016-11-25 18:39 ` Pedro Alves
2016-11-25 17:09 ` [PATCH 7/8] Fix test names starting with uppercase using multi-line gdb_test_no_output Luis Machado
2016-11-25 17:10 ` [PATCH 2/8] Fix test names starting with uppercase output by basic functions Luis Machado
2016-11-25 18:00 ` Pedro Alves
2016-11-25 17:31 ` [PATCH 0/8] Fix gdb's testsuite test names Simon Marchi
2016-11-25 17:35 ` Luis Machado
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=5cfc70b2ea19762c664d61f752c02a41@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb-patches@sourceware.org \
--cc=lgustavo@codesourcery.com \
--cc=palves@redhat.com \
/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