From: Tom Tromey <tromey@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org, jan.kratochvil@redhat.com
Subject: Re: testsuite: prefix handling
Date: Tue, 21 Feb 2012 19:17:00 -0000 [thread overview]
Message-ID: <87wr7gt63r.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4F43B6A5.3010900@redhat.com> (Pedro Alves's message of "Tue, 21 Feb 2012 15:22:13 +0000")
>>>>> "Pedro" == Pedro Alves <palves@redhat.com> writes:
>> if {$r == 0} {
Pedro> I think checking for $r == 1 (TCL_ERROR) explicitly is more correct.
I agree. My Tcl is rusty :)
Pedro> Only a few tests weren't converted to use with_test_prefix by this
Pedro> patch. Those are ones that I found that:
Pedro> - would require a large reindent
Pedro> - or with_test_prefix wasn't a 1-1 replacement
I don't mind large reindents in a situation like this.
I think the resulting code would be better.
It is up to you, though; I also don't mind the status quo.
Pedro> WDYT?
Pedro> -proc altivec_abi_tests { extra_flags force_abi } {
Pedro> +proc altivec_abi_tests { prefix extra_flags force_abi } { with_test_prefix $prefix {
[...]
Pedro> +}}
I think newlines and reindentation would result in prettier code.
The size of the diff is secondary to me; just because we'll have to read
and edit the result, not the patch.
Pedro> - altivec_abi_tests "additional_flags=-maltivec" "auto"
Pedro> + altivec_abi_tests " default ABI, auto:" "additional_flags=-maltivec" "auto"
It would be both prettier and better encapsulation if with_test_prefix
supplied the space.
Pedro> +# Test files shall make sure all the test result lines in gdb.sum are
Pedro> +# unique in a test run, so that comparing the gdb.sum files of two
Pedro> +# test runs gives correct results. Test files that exercise
Pedro> +# variations of the same tests more than once, shall prefix the
Pedro> +# different test invocations with different identifying strings in
Pedro> +# order to make them unique.
[...]
I love the comment.
Tom
next prev parent reply other threads:[~2012-02-21 19:11 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-17 19:37 [PATCH 0/2] gdb.threads/attach-into-signal.exp: prepare for gdbserver Pedro Alves
2012-02-17 19:38 ` [PATCH 1/2] gdb.threads/attach-into-signal.exp: cleanup Pedro Alves
2012-02-17 20:55 ` Tom Tromey
2012-02-17 21:00 ` Pedro Alves
2012-02-17 22:04 ` Tom Tromey
2012-02-20 13:27 ` Pedro Alves
2012-02-21 16:05 ` testsuite: prefix handling Pedro Alves
2012-02-21 18:18 ` Jan Kratochvil
2012-02-21 19:28 ` Pedro Alves
2012-02-21 19:54 ` Tom Tromey
2012-02-21 19:17 ` Tom Tromey [this message]
2012-02-21 20:08 ` Pedro Alves
2012-02-21 20:59 ` Pedro Alves
2012-02-21 21:02 ` Tom Tromey
2012-02-21 22:08 ` Pedro Alves
2012-02-21 21:00 ` Tom Tromey
2012-02-21 22:03 ` Pedro Alves
2012-02-17 21:31 ` [PATCH 1/2] gdb.threads/attach-into-signal.exp: cleanup Pedro Alves
2012-03-01 11:47 ` Pedro Alves
2012-02-17 23:55 ` Joel Brobecker
2012-02-20 8:57 ` Jan Kratochvil
2012-02-17 19:52 ` [PATCH 2/2] gdb.threads/attach-into-signal.exp: don't rely on linux native target's internal debug output Pedro Alves
2012-02-20 9:41 ` Jan Kratochvil
2012-02-20 12:32 ` Pedro Alves
2012-02-20 12:34 ` Jan Kratochvil
2012-02-20 12:37 ` Pedro Alves
2012-02-21 18:17 ` Edjunior Barbosa Machado
2012-02-21 19:11 ` Pedro Alves
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=87wr7gt63r.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.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