From: Kevin Wolf <kwolf@redhat.com>
To: John Snow <jsnow@redhat.com>
Cc: Fam Zheng <famz@redhat.com>,
qemu-devel@nongnu.org, vsementsov@virtuozzo.com,
qemu-block@nongnu.org, Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] iotests: 222: Don't run with luks
Date: Tue, 10 Jul 2018 17:45:36 +0200 [thread overview]
Message-ID: <20180710154536.GN5852@localhost.localdomain> (raw)
In-Reply-To: <fd182f4f-3205-2683-bbb7-eca3b0972609@redhat.com>
Am 10.07.2018 um 17:34 hat John Snow geschrieben:
>
>
> On 07/10/2018 05:38 AM, Fam Zheng wrote:
> > Luks needs special parameters to operate the image. Since this test is
> > focusing on image fleecing, skip skip that format.
> >
> > Signed-off-by: Fam Zheng <famz@redhat.com>
> > ---
> > tests/qemu-iotests/222 | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/tests/qemu-iotests/222 b/tests/qemu-iotests/222
> > index ff3bfc1470..0ead56d574 100644
> > --- a/tests/qemu-iotests/222
> > +++ b/tests/qemu-iotests/222
> > @@ -25,6 +25,8 @@ import iotests
> > from iotests import log, qemu_img, qemu_io, qemu_io_silent
> >
> > iotests.verify_platform(['linux'])
> > +iotests.verify_image_format(supported_fmts=['qcow2', 'qcow', 'qed', 'vmdk',
> > + 'vhdx', 'raw'])
> >
> > patterns = [("0x5d", "0", "64k"),
> > ("0xd5", "1M", "64k"),
> >
>
> Ah; do we not have a nicer way to exclude just one format? Evidently not.
iotest.verify_image_format() has an argument unsupported_fmts, but I
think a whitelist is better anyway.
Kevin
prev parent reply other threads:[~2018-07-10 15:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-10 9:38 [Qemu-devel] [PATCH] iotests: 222: Don't run with luks Fam Zheng
2018-07-10 9:58 ` Kevin Wolf
2018-07-10 15:34 ` John Snow
2018-07-10 15:45 ` Kevin Wolf [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=20180710154536.GN5852@localhost.localdomain \
--to=kwolf@redhat.com \
--cc=famz@redhat.com \
--cc=jsnow@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).