public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Luis Machado <luis.machado@linaro.org>, gdb-patches@sourceware.org
Subject: Re: [PATCH,v2 testsuite] Fix some duplicate test names
Date: Tue, 26 May 2020 18:50:08 +0100	[thread overview]
Message-ID: <1021975e-b67f-5e04-4469-2640c27add81@redhat.com> (raw)
In-Reply-To: <20200526173925.30491-1-luis.machado@linaro.org>

Hi, spotted a couple more issues:

On 5/26/20 6:39 PM, Luis Machado wrote:
>      gdb_test_multiple "$test" "$test" {
>  	-re "Breakpoint (\[0-9\]*) at .*$where.*$gdb_prompt $" {
>  	    set bp $expect_out(1,string)
> -	    pass "$test"
> +	    pass "$test inserted as number $bp"

Same issue with FAIL vs PASS messages.  This needs to be:

 -     gdb_test_multiple "$test" "$test" {
 +     gdb_test_multiple "$test" "$test inserted as number $bp" {
  	-re "Breakpoint (\[0-9\]*) at .*$where.*$gdb_prompt $" {
  	    set bp $expect_out(1,string)
 -	    pass "$test"
 +	    pass $gdb_test_name


> -    gdb_test_multiple "break *test_str_pc" "break test_str_pc" {
> +    gdb_test_multiple "break *test_str_pc" "" {
>  	-re "Breakpoint.*at.* file .*$srcfile, line.*\r\n$gdb_prompt $" {
> -	    pass "break test_str_pc"
> +	    pass $gdb_test_name
>  	}
>  	-re "No symbol.*\r\n$gdb_prompt $" {
>  	    pass "break test_str_pc"

Please update the other "-re" cases too, so they all have the
same message.  Here the pass call in the last line shown has
a different message.

Thanks,
Pedro Alves


  reply	other threads:[~2020-05-26 17:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-26 14:18 [PATCH, " Luis Machado
2020-05-26 15:35 ` Pedro Alves
2020-05-26 17:08   ` Luis Machado
2020-05-26 17:39 ` [PATCH,v2 " Luis Machado
2020-05-26 17:50   ` Pedro Alves [this message]
2020-05-26 18:42     ` Luis Machado
2020-05-26 18:53       ` Pedro Alves
2020-05-26 19:02 ` [PATCH,v3 " Luis Machado
2020-05-26 19:35   ` Pedro Alves
2020-05-26 20:23     ` Luis Machado
2020-05-26 20:52       ` Pedro Alves
2020-05-27 12:39         ` 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=1021975e-b67f-5e04-4469-2640c27add81@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=luis.machado@linaro.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).