public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [RFA 2/2] Make some test names invariant
Date: Thu, 15 Sep 2016 15:16:00 -0000	[thread overview]
Message-ID: <c0bb5a4a-3032-9266-ef7a-8b0fe3a655a1@redhat.com> (raw)
In-Reply-To: <1473893962-12420-2-git-send-email-tom@tromey.com>

On 09/14/2016 11:59 PM, Tom Tromey wrote:
> While working on the previous patch, I noticed that the test names in
> process-dies-while-detaching include the PID of some test process,
> making it so that the test names change between runs.  This patch
> fixes the problem.

LGTM.

However, FYI, with the current "definition" of test names, it 
doesn't actually change, because tools should be ignoring the
trailing " (...)" bit.  See:

 https://sourceware.org/gdb/wiki/GDBTestcaseCookbook#Do_not_use_.22tail_parentheses.22_on_test_messages

We've always had to consider this, given "$test (timeout)", etc.

Note that the wiki doesn't say it, and I don't think we've ever
discussed it, but but the space before the open parens should matter
when deciding whether to ignore the trailing bit.  If there's no space,
it shouldn't be ignored.  This in order to make it possible to write
tests that call functions without coming up with odd contortions,
like, e.g., "print foo(1)".

Thanks,
Pedro Alves

  reply	other threads:[~2016-09-15 15:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-14 22:59 [RFA 1/2] PR gdb/20604 - fix "quit" when an invalid expression is used Tom Tromey
2016-09-14 22:59 ` [RFA 2/2] Make some test names invariant Tom Tromey
2016-09-15 15:16   ` Pedro Alves [this message]
2016-09-15 16:46     ` Tom Tromey
2016-09-15 15:06 ` [RFA 1/2] PR gdb/20604 - fix "quit" when an invalid expression is used Pedro Alves
2016-09-21  7:51   ` Tom Tromey
2016-09-21 17:16     ` Pedro Alves
2016-10-26 19:44       ` Ulrich Weigand
2016-11-03 11:21         ` Pedro Alves
2016-11-07 15:57           ` Ulrich Weigand
2017-10-17 17:28             ` Pedro Alves
2017-10-20 12:55               ` Ulrich Weigand

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=c0bb5a4a-3032-9266-ef7a-8b0fe3a655a1@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tom@tromey.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).