From: Thomas Huth <thuth@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Kevin Wolf <kwolf@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Qemu-block <qemu-block@nongnu.org>, Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] tests/check-block: Skip iotests when sanitizers are enabled
Date: Fri, 23 Aug 2019 12:12:40 +0200 [thread overview]
Message-ID: <485cfb8a-5b0c-735b-8e81-586f6dbdceae@redhat.com> (raw)
In-Reply-To: <CAFEAcA_F9oscKx9zM=8=E55Ju7B72EQq2hLk1gptQ81zBEO_Ug@mail.gmail.com>
On 8/23/19 11:53 AM, Peter Maydell wrote:
> On Fri, 23 Aug 2019 at 10:35, Thomas Huth <thuth@redhat.com> wrote:
>>
>> On 8/23/19 11:04 AM, Peter Maydell wrote:
>>> On Fri, 23 Aug 2019 at 09:43, Thomas Huth <thuth@redhat.com> wrote:
>>>>
>>>> The sanitizers (especially the address sanitizer from Clang) are
>>>> sometimes printing out warnings or false positives - this spoils
>>>> the output of the iotests, causing some of the tests to fail.
>>>> Thus let's skip the automatic iotests during "make check" when the
>>>> user configured QEMU with --enable-sanitizers.
>>>
>>> Do you have a log of what the sanitizer is saying?
>>
>> https://patchew.org/logs/QEMU/testing.asan/?type=project
>
> (I get a "Not Found" error for that URL.)
Looks like Paolo just disabled the asan test in patchew and thus it got
removed.
Anyway, I can reproduce the issues also locally here with this configure
line:
configure --enable-sanitizers --target-list=x86_64-softmmu --cc=clang
--cxx=clang++
and then running "make check".
I'm using clang version 7.0.1.
Thomas
next prev parent reply other threads:[~2019-08-23 10:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-23 8:42 [Qemu-devel] [PATCH] tests/check-block: Skip iotests when sanitizers are enabled Thomas Huth
2019-08-23 9:04 ` Peter Maydell
2019-08-23 9:35 ` Thomas Huth
2019-08-23 9:53 ` Peter Maydell
2019-08-23 10:12 ` Thomas Huth [this message]
2019-08-27 17:34 ` Max Reitz
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=485cfb8a-5b0c-735b-8e81-586f6dbdceae@redhat.com \
--to=thuth@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.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 NNTP newsgroup(s).