From: John Snow <jsnow@redhat.com>
To: qemu-block@nongnu.org
Cc: kwolf@redhat.com, John Snow <jsnow@redhat.com>, qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH for-2.6 0/3] iotests: 124: Don't reopen qcow2 file
Date: Tue, 1 Dec 2015 18:16:36 -0500 [thread overview]
Message-ID: <1449011799-2790-1-git-send-email-jsnow@redhat.com> (raw)
Kevin caught me being Naughty, and because I don't want Santa to be
mad at me, I have corrected my ways.
Split iotest 124 into two classes so that the iotest that requires
a blkdebug filter from the get-go can forego the standard setUp
routine and just do it correct the first time.
Does this warrant three patches? Not really, but to make the code
motion nice to look at, I had to split it out that way.
--js
________________________________________________________________________________
For convenience, this branch is available at:
https://github.com/jnsnow/qemu.git branch block-iotest-124-qcow2-locking
https://github.com/jnsnow/qemu/tree/block-iotest-124-qcow2-locking
This version is tagged block-iotest-124-qcow2-locking-v1:
https://github.com/jnsnow/qemu/releases/tag/block-iotest-124-qcow2-locking-v1
John Snow (3):
iotests: 124: Split into two test classes
iotests: 124: move incremental failure test
iotests: 124: don't reopen qcow2
tests/qemu-iotests/124 | 148 +++++++++++++++++++++++++++----------------------
1 file changed, 81 insertions(+), 67 deletions(-)
--
2.4.3
next reply other threads:[~2015-12-01 23:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-01 23:16 John Snow [this message]
2015-12-01 23:16 ` [Qemu-devel] [PATCH for-2.6 1/3] iotests: 124: Split into two test classes John Snow
2015-12-01 23:16 ` [Qemu-devel] [PATCH for-2.6 2/3] iotests: 124: move incremental failure test John Snow
2015-12-01 23:16 ` [Qemu-devel] [PATCH for-2.6 3/3] iotests: 124: don't reopen qcow2 John Snow
2015-12-02 12:43 ` [Qemu-devel] [PATCH for-2.6 0/3] iotests: 124: Don't reopen qcow2 file 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=1449011799-2790-1-git-send-email-jsnow@redhat.com \
--to=jsnow@redhat.com \
--cc=kwolf@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).