From: Stefan Hajnoczi <stefanha@gmail.com>
To: John Snow <jsnow@redhat.com>
Cc: qemu-block@nongnu.org, kwolf@redhat.com, ldoktor@redhat.com,
qemu-devel@nongnu.org, mreitz@redhat.com
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH] iotests: fix 197 for vpc
Date: Fri, 1 Dec 2017 09:45:38 +0000 [thread overview]
Message-ID: <20171201094538.GD23501@stefanha-x1.localdomain> (raw)
In-Reply-To: <20171129224421.18192-1-jsnow@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1023 bytes --]
On Wed, Nov 29, 2017 at 05:44:21PM -0500, John Snow wrote:
> VPC has some difficulty creating geometries of particular size.
> However, we can indeed force it to use a literal one, so let's
> do that for the sake of test 197, which is testing some specific
> offsets.
>
> Signed-off-by: John Snow <jsnow@redhat.com>
> ---
> tests/qemu-iotests/197 | 3 +++
> tests/qemu-iotests/common.filter | 3 ++-
> 2 files changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/tests/qemu-iotests/197 b/tests/qemu-iotests/197
> index 887eb4f496..e1292689c1 100755
> --- a/tests/qemu-iotests/197
> +++ b/tests/qemu-iotests/197
> @@ -60,6 +60,9 @@ echo '=== Copy-on-read ==='
> echo
>
> # Prep the images
> +if [ "$IMGFMT" = "vpc" ]; then
> + IMGOPTS=$(_optstr_add "$IMGOPTS" "force_size")
> +fi
It would be nice to include a comment in the code instead of the commit
description so anyone reading knows why vpc is special-cased here.
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2017-12-01 17:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-29 22:44 [Qemu-devel] [PATCH] iotests: fix 197 for vpc John Snow
2017-11-29 23:02 ` Eric Blake
2017-11-29 23:12 ` John Snow
2017-11-30 5:11 ` Lukáš Doktor
2017-12-01 9:45 ` Stefan Hajnoczi [this message]
2017-12-05 1:08 ` [Qemu-devel] [Qemu-block] " John Snow
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=20171201094538.GD23501@stefanha-x1.localdomain \
--to=stefanha@gmail.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=ldoktor@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--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).