Re: [Qemu-devel] [PATCH 5/5] docker: Add test-block

[Daniel P. Berrange]

On Fri, May 05, 2017 at 11:23:40AM +0800, Fam Zheng wrote:
> Signed-off-by: Fam Zheng <address@hidden>
> ---
>  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 <address@hidden>
> +#
> +# 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 :|