Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Simon Marchi <simon.marchi@ericsson.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] get_integer_valueof: Don't output value in test name
Date: Tue, 10 Oct 2017 19:02:00 -0000	[thread overview]
Message-ID: <e7fa8eaa-1fdb-d25b-d07c-b3d5356e7c36@redhat.com> (raw)
In-Reply-To: <1507661462-32717-1-git-send-email-simon.marchi@ericsson.com>

On 10/10/2017 07:51 PM, Simon Marchi wrote:
> The get_integer_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.threads/process-dies-while-detaching.exp: multi-process: continue: killed outside: get integer valueof "mypid" (28770)
> +PASS: gdb.threads/process-dies-while-detaching.exp: multi-process: continue: killed outside: get integer valueof "mypid" (32238)

Ideally, test result diffing tools would be ignoring
" (foo)" at the end test names, because that part is
not considered a part of the test name itself.  It's
extra info.  That's where we write "(timeout)", "(eof)",
etc.  So for instance:

 -PASS: gdb.threads/process-dies-while-detaching.exp: multi-process: continue: killed outside: get integer valueof "mypid"
 +FAIL: gdb.threads/process-dies-while-detaching.exp: multi-process: continue: killed outside: get integer valueof "mypid" (timeout)

... this should be considered a regression, instead of a new FAIL and
a missing PASS.

I think the buildbot diffing script is correctly ignoring that
tail end "(foo)"s.

That said, I think it's still a good idea to make the gdb.sum output
more stable across passing runs, so that plain /usr/bin/diff also
works reasonable well.

> 
> This patch removes that, since it's probably not very useful.

Since we can find the number in gdb.log if we need it, this
is fine with me.

Thanks,
Pedro Alves


  reply	other threads:[~2017-10-10 19:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-10 18:51 Simon Marchi
2017-10-10 19:02 ` Pedro Alves [this message]
2017-10-10 19:10   ` Simon Marchi

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=e7fa8eaa-1fdb-d25b-d07c-b3d5356e7c36@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@ericsson.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