From: Fam Zheng <famz@redhat.com>
To: Peter Lieven <pl@kamp.de>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
ronniesahlberg@gmail.com, Jeff Cody <jcody@redhat.com>,
Max Reitz <mreitz@redhat.com>,
owasserm@redhat.com, Federico Simoncelli <fsimonce@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Wenchao Xia <xiawenc@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCHv2 04/18] qemu-iotests: fix test 013 to work with any protocol
Date: Mon, 06 Jan 2014 13:31:46 +0800 [thread overview]
Message-ID: <52CA3FC2.8060609@redhat.com> (raw)
In-Reply-To: <1388942528-10453-5-git-send-email-pl@kamp.de>
On 2014年01月06日 01:21, Peter Lieven wrote:
> Signed-off-by: Peter Lieven <pl@kamp.de>
> ---
> tests/qemu-iotests/013 | 9 ++++-----
> tests/qemu-iotests/013.out | 2 +-
> 2 files changed, 5 insertions(+), 6 deletions(-)
>
> diff --git a/tests/qemu-iotests/013 b/tests/qemu-iotests/013
> index ea3cab9..0dbc934 100755
> --- a/tests/qemu-iotests/013
> +++ b/tests/qemu-iotests/013
> @@ -41,14 +41,14 @@ trap "_cleanup; exit \$status" 0 1 2 3 15
>
> # much of this could be generic for any format supporting compression.
> _supported_fmt qcow qcow2
> -_supported_proto file
> +_supported_proto generic
> _supported_os Linux
>
> TEST_OFFSETS="0 4294967296"
> TEST_OPS="writev read write readv"
> CLUSTER_SIZE=4096
>
I think dropping these three TEST_IMG overriding change...
> -_make_test_img 6G
> +TEST_IMG=$TEST_IMG.orig _make_test_img 6G
#1
>
> echo "Testing empty image"
> echo
> @@ -56,16 +56,15 @@ echo
> for offset in $TEST_OFFSETS; do
> echo "At offset $offset:"
> for op in $TEST_OPS; do
> - io_test $op $offset $CLUSTER_SIZE 8
> + TEST_IMG=$TEST_IMG.orig io_test $op $offset $CLUSTER_SIZE 8
#2
> done
> - _check_test_img
> + TEST_IMG=$TEST_IMG.orig _check_test_img
#3
> done
>
>
> echo "Compressing image"
> echo
>
> -mv "$TEST_IMG" "$TEST_IMG.orig"
and changing this to
TEST_IMG=$TEST_IMG.orig _make_test_img 6G
Should work.
> $QEMU_IMG convert -f $IMGFMT -O $IMGFMT -c "$TEST_IMG.orig" "$TEST_IMG"
>
> echo "Testing compressed image"
> diff --git a/tests/qemu-iotests/013.out b/tests/qemu-iotests/013.out
> index 43a414c..763cb0c 100644
> --- a/tests/qemu-iotests/013.out
> +++ b/tests/qemu-iotests/013.out
> @@ -1,5 +1,5 @@
> QA output created by 013
> -Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=6442450944
> +Formatting 'TEST_DIR/t.IMGFMT.orig', fmt=IMGFMT size=6442450944
So this is not necessary.
Fam
next prev parent reply other threads:[~2014-01-06 5:32 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-05 17:21 [Qemu-devel] [PATCHv2 00/18] qemu-iotests: adjust tests to work with the NFS protocol Peter Lieven
2014-01-05 17:21 ` [Qemu-devel] [PATCHv2 01/18] qemu-iotests: change _supported_proto to file for various tests Peter Lieven
2014-01-05 17:21 ` [Qemu-devel] [PATCHv2 02/18] qemu-iotests: enable support for NFS protocol Peter Lieven
2014-01-06 20:14 ` Jeff Cody
2014-01-06 22:19 ` Peter Lieven
2014-01-05 17:21 ` [Qemu-devel] [PATCHv2 03/18] qemu-iotests: enable test 016 and 025 to work with " Peter Lieven
2014-01-05 17:21 ` [Qemu-devel] [PATCHv2 04/18] qemu-iotests: fix test 013 to work with any protocol Peter Lieven
2014-01-06 5:31 ` Fam Zheng [this message]
2014-01-06 6:48 ` Peter Lieven
2014-01-06 10:09 ` Fam Zheng
2014-01-06 12:21 ` Peter Lieven
2014-01-06 12:47 ` Fam Zheng
2014-01-06 20:40 ` Jeff Cody
2014-01-06 22:35 ` Peter Lieven
2014-01-05 17:21 ` [Qemu-devel] [PATCHv2 05/18] qemu-iotests: fix tests 014 and 023 " Peter Lieven
2014-01-06 5:40 ` Fam Zheng
2014-01-06 6:49 ` Peter Lieven
2014-01-10 19:04 ` Kevin Wolf
2014-01-10 19:06 ` Peter Lieven
2014-01-10 19:14 ` Kevin Wolf
2014-01-10 19:36 ` Peter Lieven
2014-01-05 17:21 ` [Qemu-devel] [PATCHv2 06/18] qemu-iotests: fix test 018 " Peter Lieven
2014-01-06 5:45 ` Fam Zheng
2014-01-05 17:21 ` [Qemu-devel] [PATCHv2 07/18] qemu-iotests: fix test 019 " Peter Lieven
2014-01-05 17:21 ` [Qemu-devel] [PATCHv2 08/18] qemu-iotests: fix test 020 " Peter Lieven
2014-01-05 17:21 ` [Qemu-devel] [PATCHv2 09/18] qemu-iotests: fix test 024 " Peter Lieven
2014-01-05 17:22 ` [Qemu-devel] [PATCHv2 10/18] qemu-iotests: fix test 028 " Peter Lieven
2014-01-05 17:22 ` [Qemu-devel] [PATCHv2 11/18] qemu-iotests: fix test 034 " Peter Lieven
2014-01-05 17:22 ` [Qemu-devel] [PATCHv2 12/18] qemu-iotests: fix test 037 " Peter Lieven
2014-01-05 17:22 ` [Qemu-devel] [PATCHv2 13/18] qemu-iotests: fix test 038 " Peter Lieven
2014-01-05 17:22 ` [Qemu-devel] [PATCHv2 14/18] qemu-iotests: fix test 043 " Peter Lieven
2014-01-05 17:22 ` [Qemu-devel] [PATCHv2 15/18] qemu-iotests: fix test 046 " Peter Lieven
2014-01-05 17:22 ` [Qemu-devel] [PATCHv2 16/18] qemu-iotests: fix expected output of test 067 Peter Lieven
2014-01-05 17:22 ` [Qemu-devel] [PATCHv2 17/18] qemu-iotests: blacklist test 020 for NFS protocol Peter Lieven
2014-01-06 5:51 ` Fam Zheng
2014-01-06 6:41 ` Peter Lieven
2014-01-05 17:22 ` [Qemu-devel] [PATCHv2 18/18] qemu-iotests: test 026 store blkdebug.cfg locally Peter Lieven
2014-02-24 12:54 ` [Qemu-devel] [PATCHv2 00/18] qemu-iotests: adjust tests to work with the NFS protocol Stefan Hajnoczi
2014-02-24 20:21 ` Peter Lieven
2014-02-25 10:49 ` Stefan Hajnoczi
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=52CA3FC2.8060609@redhat.com \
--to=famz@redhat.com \
--cc=fsimonce@redhat.com \
--cc=jcody@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=owasserm@redhat.com \
--cc=pl@kamp.de \
--cc=qemu-devel@nongnu.org \
--cc=ronniesahlberg@gmail.com \
--cc=stefanha@redhat.com \
--cc=xiawenc@linux.vnet.ibm.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).