From: Simon Marchi <simon.marchi@polymtl.ca>
To: Tom de Vries <tdevries@suse.de>
Cc: gdb-patches@sourceware.org,
Simon Marchi <simon.marchi@ericsson.com>,
Pedro Alves <palves@redhat.com>
Subject: Re: [PATCH][gdb/testsuite] get_valueof: Don't output value in test name
Date: Wed, 31 Oct 2018 16:43:00 -0000 [thread overview]
Message-ID: <d5a6c864cbc3ce5380c29ddd2df5f442@polymtl.ca> (raw)
In-Reply-To: <20181031162744.GA27881@delia>
On 2018-10-31 12:27, Tom de Vries wrote:
> Hi,
>
> The get_valueof outputs the value it has read as part of the test name.
> This
> causes test names to vary from run to run, and adds some noise when
> diffing
> test results. e.g.:
>
> -PASS: gdb.guile/scm-ports.exp: buffered: get valueof "$sp"
> (140737488343920)
> +PASS: gdb.guile/scm-ports.exp: buffered: get valueof "$sp"
> (140737488343968)
> -PASS: gdb.guile/scm-ports.exp: unbuffered: get valueof "$sp"
> (140737488343920)
> +PASS: gdb.guile/scm-ports.exp: unbuffered: get valueof "$sp"
> (140737488343968)
>
> This patch removes that, since it's probably not very useful.
>
> Tested on x86_64-linux.
>
> OK for trunk?
>
> Thanks,
> - Tom
>
> [gdb/testsuite] get_valueof: Don't output value in test name
>
> 2018-10-31 Tom de Vries <tdevries@suse.de>
>
> * lib/gdb.exp (get_valueof): Don't output read value in test name.
>
> ---
> gdb/testsuite/lib/gdb.exp | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/gdb/testsuite/lib/gdb.exp b/gdb/testsuite/lib/gdb.exp
> index b4cf80e38a..5a5713b114 100644
> --- a/gdb/testsuite/lib/gdb.exp
> +++ b/gdb/testsuite/lib/gdb.exp
> @@ -5636,7 +5636,7 @@ proc get_valueof { fmt exp default {test ""} } {
> gdb_test_multiple "print${fmt} ${exp}" "$test" {
> -re "\\$\[0-9\]* = (\[^\r\n\]*)\[\r\n\]*$gdb_prompt $" {
> set val $expect_out(1,string)
> - pass "$test ($val)"
> + pass "$test"
> }
> timeout {
> fail "$test (timeout)"
LGTM, thanks.
Simon
prev parent reply other threads:[~2018-10-31 16:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-31 16:27 Tom de Vries
2018-10-31 16:43 ` Simon Marchi [this message]
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=d5a6c864cbc3ce5380c29ddd2df5f442@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=simon.marchi@ericsson.com \
--cc=tdevries@suse.de \
/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