From: Max Reitz <mreitz@redhat.com>
To: Eric Blake <eblake@redhat.com>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v6 12/14] iotests: Add test for backing-chain commits
Date: Fri, 02 May 2014 15:15:33 +0200 [thread overview]
Message-ID: <53639A75.4040303@redhat.com> (raw)
In-Reply-To: <536069B9.2050409@redhat.com>
On 30.04.2014 05:10, Eric Blake wrote:
> On 04/29/2014 09:17 AM, Max Reitz wrote:
>> Add a test for qemu-img commit on backing chains with more than two
>> images. This test also checks whether the images above the base image
>> are emptied and does therefore not work for qed and vmdk which requires
>> it to be separate from 020.
>>
>> Signed-off-by: Max Reitz <mreitz@redhat.com>
>> ---
>> tests/qemu-iotests/092 | 108 +++++++++++++++++++++++++++++++++++++++++++++
>> tests/qemu-iotests/092.out | 59 +++++++++++++++++++++++++
>> tests/qemu-iotests/group | 1 +
>> 3 files changed, 168 insertions(+)
>> create mode 100755 tests/qemu-iotests/092
>> create mode 100644 tests/qemu-iotests/092.out
>>
>> +# Two passes:
>> +# 0: Two-layer backing chain, commit to upper backing file (default)
>> +# (in this case, the top image will be emptied)
>> +# 1: Two-layer backing chain, commit to lower backing file
>> +# (in this case, the top image will stay as it is)
> Should this test be modified to test the new -d option?
Probably, yes, I'll include another pass.
Max
next parent reply other threads:[~2014-05-02 13:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1398784072-3319-1-git-send-email-mreitz@redhat.com>
[not found] ` <1398784640-3797-1-git-send-email-mreitz@redhat.com>
[not found] ` <536069B9.2050409@redhat.com>
2014-05-02 13:15 ` Max Reitz [this message]
[not found] ` <1398784072-3319-4-git-send-email-mreitz@redhat.com>
[not found] ` <5360268A.8080100@redhat.com>
2014-05-02 13:45 ` [Qemu-devel] [PATCH v6 03/14] qcow2: Optimize bdrv_make_empty() Max Reitz
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=53639A75.4040303@redhat.com \
--to=mreitz@redhat.com \
--cc=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.