From: Pedro Alves <palves@redhat.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: Andrew Burgess <andrew.burgess@embecosm.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH 2/2] gdb: Make some test names unique
Date: Thu, 22 Jun 2017 12:06:00 -0000 [thread overview]
Message-ID: <ae560322-2203-ec37-e40d-22d962a4ed96@redhat.com> (raw)
In-Reply-To: <CAH=s-PNf8xHRCPzLsf3Ub8Wa=pz+h1O-ij=P2a1TeTRQT0VbuQ@mail.gmail.com>
On 06/22/2017 12:59 PM, Yao Qi wrote:
> On Thu, Jun 22, 2017 at 12:08 PM, Pedro Alves <palves@redhat.com> wrote:
>> On 06/22/2017 11:37 AM, Yao Qi wrote:
>>> Andrew Burgess <andrew.burgess@embecosm.com> writes:
>>>
>>>
>>>> mi_gdb_test "540-data-evaluate-expression vla1(1)" \
>>>> - "540\\^done,value=\"1\"" "evaluate filled vla"
>>>> + "540\\^done,value=\"1\"" "evaluate filled vla(1)"
>>>
>>> Do not use "tail parentheses" on the test message,
>>> https://sourceware.org/gdb/wiki/GDBTestcaseCookbook#Do_not_use_.22tail_parentheses.22_on_test_messages
>>
>> The wiki doesn't mention it, but I think the rule should only apply when
>> there's a space before the parens.
>
> I wanted to get confirm from analyze-racy-logs.py,
> but I was lost in it, so I decided to follow the wiki.
I only realized the need for the tweak to the rule after
the original discussion that led to the rule being added
to the wiki, and this is the first time I'm suggesting it,
I think.
>>
>> I don't think it's worth it, or even a good idea to try to
>> come up with different test names for all of these. In cases like
>> these, I think it's generally possible to avoid the space before
>> the parens. So IMO, we should clarify the rule instead
>> (and the buildbot testresult diffing accordingly, if necessary).
>>
>
> The current rule is "When you write a test, do not
> put text between parentheses at the end of the text
> message", we can change it "when you write a test,
> do not put text between parentheses at the end of
> the text message and space before parentheses".
>
> They are OK,
> PASS: gdb.base/foo.exp: whatever test
> FAIL: gdb.base/foo.exp: whatever test (timeout)
> PASS: gdb.base/foo.exp: whatever test(1st)
> PASS: gdb.base/foo.exp: whatever test(2nd)
>
> They are not OK,
> PASS: gdb.trace/trace-break.exp: 2 trace trace on: trace set_point (1)
> PASS: gdb.trace/trace-break.exp: 2 trace trace on: trace set_point (2)
>
> Is it right?
Yes.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2017-06-22 12:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-14 18:57 [PATCH 0/2] Couple of small fixes to gdb.mi/mi-vla-fortran.exp test Andrew Burgess
2017-06-14 18:58 ` [PATCH 2/2] gdb: Make some test names unique Andrew Burgess
2017-06-22 10:37 ` Yao Qi
2017-06-22 11:08 ` Pedro Alves
[not found] ` <CAH=s-PNf8xHRCPzLsf3Ub8Wa=pz+h1O-ij=P2a1TeTRQT0VbuQ@mail.gmail.com>
2017-06-22 12:06 ` Pedro Alves [this message]
2017-06-22 12:12 ` Pedro Alves
2017-07-13 20:15 ` [PATCHv2 " Andrew Burgess
2017-07-13 22:40 ` Pedro Alves
2017-06-14 18:58 ` [PATCH 1/2] gdb: Fix parameter passing to mi_create_breakpoint Andrew Burgess
2017-06-22 10:16 ` Yao Qi
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=ae560322-2203-ec37-e40d-22d962a4ed96@redhat.com \
--to=palves@redhat.com \
--cc=andrew.burgess@embecosm.com \
--cc=gdb-patches@sourceware.org \
--cc=qiyaoltc@gmail.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