From: no-reply@patchew.org
To: mlevitsk@redhat.com
Cc: kwolf@redhat.com, mlevitsk@redhat.com, vsementsov@virtuozzo.com,
berrange@redhat.com, qemu-block@nongnu.org,
qemu-devel@nongnu.org, qemu-stable@nongnu.org, mreitz@redhat.com
Subject: Re: [Qemu-devel] [PATCH v6 0/3] Fix qcow2+luks corruption introduced by commit 8ac0f15f335
Date: Fri, 13 Sep 2019 17:28:29 -0700 (PDT) [thread overview]
Message-ID: <156842090797.31080.6142961078768911120@5dec9699b7de> (raw)
In-Reply-To: <20190913172741.5662-1-mlevitsk@redhat.com>
Patchew URL: https://patchew.org/QEMU/20190913172741.5662-1-mlevitsk@redhat.com/
Hi,
This series failed the docker-quick@centos7 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
make docker-image-centos7 V=1 NETWORK=1
time make docker-test-quick@centos7 SHOW_ENV=1 J=14 NETWORK=1
=== TEST SCRIPT END ===
libudev no
default devices yes
warning: Python 2 support is deprecated
warning: Python 3 will be required for building future versions of QEMU
cross containers no
NOTE: guest cross-compilers enabled: cc
The full log is available at
http://patchew.org/logs/20190913172741.5662-1-mlevitsk@redhat.com/testing.docker-quick@centos7/?type=message.
---
Email generated automatically by Patchew [https://patchew.org/].
Please send your feedback to patchew-devel@redhat.com
prev parent reply other threads:[~2019-09-14 0:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-13 17:27 [Qemu-devel] [PATCH v6 0/3] Fix qcow2+luks corruption introduced by commit 8ac0f15f335 Maxim Levitsky
2019-09-13 17:27 ` [Qemu-devel] [PATCH v6 1/3] " Maxim Levitsky
2019-09-13 17:27 ` [Qemu-devel] [PATCH v6 2/3] block/qcow2: refactor threaded encryption code Maxim Levitsky
2019-09-13 17:51 ` Vladimir Sementsov-Ogievskiy
2019-09-13 18:19 ` Maxim Levitsky
2019-09-13 18:37 ` Vladimir Sementsov-Ogievskiy
2019-09-13 17:27 ` [Qemu-devel] [PATCH v6 3/3] qemu-iotests: Add test for bz #1745922 Maxim Levitsky
2019-09-14 0:28 ` no-reply [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=156842090797.31080.6142961078768911120@5dec9699b7de \
--to=no-reply@patchew.org \
--cc=berrange@redhat.com \
--cc=kwolf@redhat.com \
--cc=mlevitsk@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=vsementsov@virtuozzo.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 NNTP newsgroup(s).