From: "Daniel P. Berrange" <berrange@redhat.com>
To: Fam Zheng <famz@redhat.com>
Cc: qemu-devel@nongnu.org, "Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [Qemu-devel] [PATCH 5/5] docker: Add test-block
Date: Mon, 8 May 2017 16:52:37 +0100 [thread overview]
Message-ID: <20170508155237.GW18871@redhat.com> (raw)
In-Reply-To: <20170505032340.26467-6-famz@redhat.com>
On Fri, May 05, 2017 at 11:23:40AM +0800, Fam Zheng wrote:
> Signed-off-by: Fam Zheng <famz@redhat.com>
> ---
> tests/docker/test-block | 21 +++++++++++++++++++++
> 1 file changed, 21 insertions(+)
> create mode 100755 tests/docker/test-block
>
> diff --git a/tests/docker/test-block b/tests/docker/test-block
> new file mode 100755
> index 0000000..20ef705
> --- /dev/null
> +++ b/tests/docker/test-block
> @@ -0,0 +1,21 @@
> +#!/bin/bash -e
> +#
> +# Run block test cases
> +#
> +# Copyright (c) 2017 Red Hat Inc.
> +#
> +# Authors:
> +# Fam Zheng <famz@redhat.com>
> +#
> +# This work is licensed under the terms of the GNU GPL, version 2
> +# or (at your option) any later version. See the COPYING file in
> +# the top-level directory.
> +
> +. common.rc
> +
> +cd "$BUILD_DIR"
> +
> +build_qemu --target-list=x86_64-softmmu
> +cd tests/qemu-iotests
> +./check -raw
> +./check -qcow2
qcow v1 should be passing all tests now too, so pleae include
that.
I also want to have LUKS support included, though that is pending
a couple of patches to fix some current failures
https://lists.gnu.org/archive/html/qemu-devel/2017-05/msg00277.html
If we add more tests though, this single 'test-block' job is going
to get pretty slow. qcow v1 is massively slower to complete tests
than qcow v2, and luks is quite alot slower too - particularly if
you enable the cryptsetup interoperability test case (it takes about
5 minutes to run now)
Should we have separate jobs to parallelize this across different
I/O backends.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2017-05-08 15:52 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-05 3:23 [Qemu-devel] [PATCH 0/5] docker: Add test-block Fam Zheng
2017-05-05 3:23 ` [Qemu-devel] [PATCH 1/5] docker: Run tests with current user Fam Zheng
2017-05-05 8:25 ` Alex Bennée
2017-05-06 16:25 ` Philippe Mathieu-Daudé
2017-05-05 3:23 ` [Qemu-devel] [PATCH 2/5] docker: Add bzip2 and hostname to fedora image Fam Zheng
2017-05-05 8:25 ` Alex Bennée
2017-05-06 16:34 ` Philippe Mathieu-Daudé
2017-05-05 3:23 ` [Qemu-devel] [PATCH 3/5] docker: Use unconfined security profile Fam Zheng
2017-05-05 8:27 ` Alex Bennée
2017-05-05 9:12 ` Fam Zheng
2017-05-06 16:33 ` Philippe Mathieu-Daudé
2017-05-05 3:23 ` [Qemu-devel] [PATCH 4/5] docker: Add libaio to fedora image Fam Zheng
2017-05-05 8:27 ` Alex Bennée
2017-05-06 16:26 ` Philippe Mathieu-Daudé
2017-05-05 3:23 ` [Qemu-devel] [PATCH 5/5] docker: Add test-block Fam Zheng
2017-05-05 8:28 ` Alex Bennée
2017-05-05 8:55 ` Fam Zheng
2017-05-08 15:11 ` Yash Mankad
2017-05-08 15:52 ` Daniel P. Berrange [this message]
2017-05-05 7:44 ` [Qemu-devel] [PATCH 0/5] " Paolo Bonzini
2017-05-05 8:05 ` Fam Zheng
2017-05-05 8:07 ` Paolo Bonzini
2017-05-05 8:52 ` Fam Zheng
2017-05-08 15:55 ` Daniel P. Berrange
2017-05-08 16:06 ` Paolo Bonzini
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=20170508155237.GW18871@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=famz@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).