From: "Michael S. Tsirkin" <mst@redhat.com>
To: qemu-devel@nongnu.org
Cc: ddstreet@canonical.com, Peter Maydell <peter.maydell@linaro.org>,
amorenoz@redhat.com, pezhang@redhat.com
Subject: asan: false positive? (Was Re: [Qemu-devel] [PATCH v2] vhost-user: save features if the char dev is closed)
Date: Tue, 24 Sep 2019 11:56:50 -0400 [thread overview]
Message-ID: <20190924115524-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <156882660456.17151.6049472857437201023@5dec9699b7de>
On Wed, Sep 18, 2019 at 10:10:05AM -0700, no-reply@patchew.org wrote:
> Patchew URL: https://patchew.org/QEMU/20190918084834.9729-1-amorenoz@redhat.com/
>
>
>
> Hi,
>
> This series failed the asan build test. Please find the testing commands and
> their output below. If you have Docker installed, you can probably reproduce it
> locally.
>
> === TEST SCRIPT BEGIN ===
> #!/bin/bash
> export ARCH=x86_64
> make docker-image-fedora V=1 NETWORK=1
> time make docker-test-debug@fedora TARGET_LIST=x86_64-softmmu J=14 NETWORK=1
> === TEST SCRIPT END ===
>
> CC qobject/qlit.o
> CC qobject/qjson.o
>
> Encoding error:
> 'utf-8' codec can't decode byte 0x95 in position 799: invalid start byte
> The full traceback has been saved in /tmp/sphinx-err-mhg776xj.log, if you want to report the issue to the developers.
> CC qobject/qobject.o
>
>
> The full log is available at
> http://patchew.org/logs/20190918084834.9729-1-amorenoz@redhat.com/testing.asan/?type=message.
What happened here?
Does anyone know?
> ---
> Email generated automatically by Patchew [https://patchew.org/].
> Please send your feedback to patchew-devel@redhat.com
prev parent reply other threads:[~2019-09-24 17:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-18 8:48 [Qemu-devel] [PATCH v2] vhost-user: save features if the char dev is closed Adrian Moreno
2019-09-18 17:10 ` no-reply
2019-09-24 15:56 ` Michael S. Tsirkin [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=20190924115524-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=amorenoz@redhat.com \
--cc=ddstreet@canonical.com \
--cc=peter.maydell@linaro.org \
--cc=pezhang@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.