From: no-reply@patchew.org
To: marcandre.lureau@redhat.com
Cc: fam@euphon.net, qemu-devel@nongnu.org, otubo@redhat.com,
pbonzini@redhat.com, david@gibson.dropbear.id.au
Subject: Re: [Qemu-devel] [PATCH] vl: fix -sandbox parsing crash when seccomp support is disabled
Date: Wed, 1 May 2019 05:33:33 -0700 (PDT) [thread overview]
Message-ID: <155671401236.10667.11403551007670440961@c2072b67cc0c> (raw)
In-Reply-To: <20190429134757.13570-1-marcandre.lureau@redhat.com>
Patchew URL: https://patchew.org/QEMU/20190429134757.13570-1-marcandre.lureau@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
time make docker-test-debug@fedora TARGET_LIST=x86_64-softmmu J=14 NETWORK=1
=== TEST SCRIPT END ===
The full log is available at
http://patchew.org/logs/20190429134757.13570-1-marcandre.lureau@redhat.com/testing.asan/?type=message.
---
Email generated automatically by Patchew [https://patchew.org/].
Please send your feedback to patchew-devel@redhat.com
WARNING: multiple messages have this Message-ID (diff)
From: no-reply@patchew.org
To: marcandre.lureau@redhat.com
Cc: fam@euphon.net, otubo@redhat.com, qemu-devel@nongnu.org,
marcandre.lureau@redhat.com, pbonzini@redhat.com,
david@gibson.dropbear.id.au
Subject: Re: [Qemu-devel] [PATCH] vl: fix -sandbox parsing crash when seccomp support is disabled
Date: Wed, 1 May 2019 05:33:33 -0700 (PDT) [thread overview]
Message-ID: <155671401236.10667.11403551007670440961@c2072b67cc0c> (raw)
Message-ID: <20190501123333.9HbXgaKKcL2gGzCJICx62rfSEkFpuma3i-Ps_R5wdI0@z> (raw)
In-Reply-To: <20190429134757.13570-1-marcandre.lureau@redhat.com>
Patchew URL: https://patchew.org/QEMU/20190429134757.13570-1-marcandre.lureau@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
time make docker-test-debug@fedora TARGET_LIST=x86_64-softmmu J=14 NETWORK=1
=== TEST SCRIPT END ===
The full log is available at
http://patchew.org/logs/20190429134757.13570-1-marcandre.lureau@redhat.com/testing.asan/?type=message.
---
Email generated automatically by Patchew [https://patchew.org/].
Please send your feedback to patchew-devel@redhat.com
next prev parent reply other threads:[~2019-05-02 8:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-29 13:47 [Qemu-devel] [PATCH] vl: fix -sandbox parsing crash when seccomp support is disabled Marc-André Lureau
2019-04-29 13:47 ` Marc-André Lureau
2019-04-29 14:08 ` Philippe Mathieu-Daudé
2019-04-29 14:08 ` Philippe Mathieu-Daudé
2019-04-29 14:24 ` Laurent Vivier
2019-04-29 14:24 ` Laurent Vivier
2019-04-29 14:46 ` Marc-André Lureau
2019-04-29 14:46 ` Marc-André Lureau
2019-04-29 19:13 ` Laurent Vivier
2019-04-29 19:13 ` Laurent Vivier
2019-04-29 14:36 ` Andrea Bolognani
2019-04-29 14:36 ` Andrea Bolognani
2019-04-30 18:46 ` Paolo Bonzini
2019-04-30 18:46 ` Paolo Bonzini
2019-05-01 10:51 ` no-reply
2019-05-01 10:51 ` no-reply
2019-05-01 12:33 ` no-reply [this message]
2019-05-01 12:33 ` no-reply
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=155671401236.10667.11403551007670440961@c2072b67cc0c \
--to=no-reply@patchew.org \
--cc=david@gibson.dropbear.id.au \
--cc=fam@euphon.net \
--cc=marcandre.lureau@redhat.com \
--cc=otubo@redhat.com \
--cc=pbonzini@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 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).