public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Yuri Gribov <tetra2005@gmail.com>
To: Thomas Preudhomme <thomas.preudhomme@foss.arm.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Ignore random output from Asan tests in dg-cmp-results
Date: Mon, 10 Jul 2017 09:44:00 -0000	[thread overview]
Message-ID: <CAJOtW+7pbTRiHx1isHU=A4XkURh_ta-22JVUgrSSMYCABh86RA@mail.gmail.com> (raw)
In-Reply-To: <a0e56151-1179-a314-fc90-b1d44b38bd33@foss.arm.com>

On Mon, Jul 10, 2017 at 10:32 AM, Thomas Preudhomme
<thomas.preudhomme@foss.arm.com> wrote:
> Hi Yuri,
>
> On 09/07/17 20:06, Yuri Gribov wrote:
>>
>> Hi,
>>
>> Currently dg-cmp-results fails to compare fails in Asan tests because
>> their output includes failing process id:
>> NA->FAIL: c-c++-common/asan/bitfield-1.c   -O0  output pattern test,
>> is ==18161==ERROR
>> FAIL->NA: c-c++-common/asan/bitfield-1.c   -O0  output pattern test,
>> is ==26667==ERROR
>>
>> This patch fixes this. I also did some fairly standard refactoring to
>> improve stability and get rid of code dup.
>
>
> I'm not familiar with asan but why not fix asan tests to not print the pid
> instead?

The error message is printed by Asan runtime, not by tests themselves.
Asan maintainers are typically unwilling to change output format of
their messages as there may already be users who rely on it (e.g.
using specific regexes in their scripts, etc.).

Note that I'd very much rather fix the test (as I do in another patch
here: https://gcc.gnu.org/ml/gcc-patches/2017-07/msg00422.html).

-Y

  reply	other threads:[~2017-07-10  9:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-09 19:06 Yuri Gribov
2017-07-10  9:32 ` Thomas Preudhomme
2017-07-10  9:44   ` Yuri Gribov [this message]
2017-07-10 21:21     ` Mike Stump
2017-07-10 21:53       ` Mike Stump
2017-07-11  6:51         ` Yuri Gribov
2017-07-10 12:13 ` Thomas Preudhomme
2017-07-10 12:32   ` Yuri Gribov
2017-07-10 18:27 ` Mike Stump

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='CAJOtW+7pbTRiHx1isHU=A4XkURh_ta-22JVUgrSSMYCABh86RA@mail.gmail.com' \
    --to=tetra2005@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=thomas.preudhomme@foss.arm.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).