From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, Stefan Hajnoczi <stefanha@redhat.com>
Subject: [Qemu-devel] [PATCH 0/4] qemu-iotests: reduce iotests.py code duplication
Date: Tue, 28 May 2013 17:11:33 +0200 [thread overview]
Message-ID: <1369753897-15140-1-git-send-email-stefanha@redhat.com> (raw)
Tests 030 and 041 are written in Python and use the iotests.py module. Push
common code down into iotests.py. My 'drive-backup' series takes advantage
will take advantage of this - kwolf pointed out that earlier revisions were
duplicating too much code.
I decided to split this into a separate patch series and send it before the
next 'drive-backup' revision.
Stefan Hajnoczi (4):
qemu-iotests: make assert_no_active_block_jobs() common
qemu-iotests: make cancel_and_wait() common
qemu-iotests: make compare_images() common
qemu-iotests: make create_image() common
tests/qemu-iotests/030 | 99 ++++++++---------------
tests/qemu-iotests/041 | 181 +++++++++++++++---------------------------
tests/qemu-iotests/iotests.py | 38 +++++++++
3 files changed, 135 insertions(+), 183 deletions(-)
--
1.8.1.4
next reply other threads:[~2013-05-28 15:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-28 15:11 Stefan Hajnoczi [this message]
2013-05-28 15:11 ` [Qemu-devel] [PATCH 1/4] qemu-iotests: make assert_no_active_block_jobs() common Stefan Hajnoczi
2013-05-28 15:11 ` [Qemu-devel] [PATCH 2/4] qemu-iotests: make cancel_and_wait() common Stefan Hajnoczi
2013-05-29 9:54 ` Kevin Wolf
2013-05-29 11:02 ` Stefan Hajnoczi
2013-05-28 15:11 ` [Qemu-devel] [PATCH 3/4] qemu-iotests: make compare_images() common Stefan Hajnoczi
2013-05-28 15:11 ` [Qemu-devel] [PATCH 4/4] qemu-iotests: make create_image() common Stefan Hajnoczi
2013-05-29 5:29 ` [Qemu-devel] [PATCH 0/4] qemu-iotests: reduce iotests.py code duplication Fam Zheng
2013-05-29 7:51 ` Stefan Hajnoczi
2013-05-29 10:04 ` Kevin Wolf
2013-05-29 11:56 ` Kevin Wolf
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=1369753897-15140-1-git-send-email-stefanha@redhat.com \
--to=stefanha@redhat.com \
--cc=kwolf@redhat.com \
--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).