From: Eric Blake <eblake@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
qemu-block@nongnu.org
Cc: qemu-devel@nongnu.org, mreitz@redhat.com
Subject: Re: [PATCH] qemu-iotests: restrict 264 to qcow2 only
Date: Fri, 25 Oct 2019 10:38:21 -0500 [thread overview]
Message-ID: <6284b05a-192b-0a63-6767-145a4a832424@redhat.com> (raw)
In-Reply-To: <20191025145023.6182-1-vsementsov@virtuozzo.com>
On 10/25/19 9:50 AM, Vladimir Sementsov-Ogievskiy wrote:
> 264 is unprepared to run with different formats, for example luks needs
> handling keys, cloop doesn't support image creation, vpc creates image
> larger than requested (which breaks "Backup completed: 5242880" in test
> output).
>
> The test is here to check nbd-reconnect feature and we actually don't
> need it for all formats. Let's restrict it to qcow2 only.
>
> Reported-by: Max Reitz <mreitz@redhat.com>
> Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
> ---
> tests/qemu-iotests/264 | 2 ++
> 1 file changed, 2 insertions(+)
Reviewed-by: Eric Blake <eblake@redhat.com>
I will queue through my NBD tree; it may miss soft freeze (due to my
travel schedule for KVM Forum), but is definite 4.2 material, so it will
be in by rc1.
>
> diff --git a/tests/qemu-iotests/264 b/tests/qemu-iotests/264
> index c8cd97ae2b..131366422b 100755
> --- a/tests/qemu-iotests/264
> +++ b/tests/qemu-iotests/264
> @@ -24,6 +24,8 @@ import iotests
> from iotests import qemu_img_create, qemu_io_silent_check, file_path, \
> qemu_nbd_popen, log
>
> +iotests.verify_image_format(supported_fmts=['qcow2'])
> +
> disk_a, disk_b, nbd_sock = file_path('disk_a', 'disk_b', 'nbd-sock')
> nbd_uri = 'nbd+unix:///?socket=' + nbd_sock
> size = 5 * 1024 * 1024
>
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2019-10-25 15:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-25 14:50 [PATCH] qemu-iotests: restrict 264 to qcow2 only Vladimir Sementsov-Ogievskiy
2019-10-25 15:38 ` Eric Blake [this message]
2019-10-28 12:08 ` Max Reitz
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=6284b05a-192b-0a63-6767-145a4a832424@redhat.com \
--to=eblake@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@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).