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 v3 5/5] iotests: Add test for relative backing file names
Date: Wed, 26 Nov 2014 10:24:02 +0100 [thread overview]
Message-ID: <54759C32.1040301@redhat.com> (raw)
In-Reply-To: <5474FD52.2020207@redhat.com>
On 2014-11-25 at 23:06, Eric Blake wrote:
> On 11/24/2014 02:43 AM, Max Reitz wrote:
>> Sometimes, qemu does not have a filename to work with, so it does not
>> know which directory to use for a backing file specified by a relative
>> filename. Add a test which tests that qemu exits with an appropriate
>> error message.
>>
>> Additionally, add a test for qemu-img create with a backing filename
>> relative to the backed image's base directory while omitting the image
>> size.
>>
>> Signed-off-by: Max Reitz <mreitz@redhat.com>
>> ---
>> tests/qemu-iotests/110 | 94 ++++++++++++++++++++++++++++++++++++++++++++++
>> tests/qemu-iotests/110.out | 19 ++++++++++
>> tests/qemu-iotests/group | 1 +
>> 3 files changed, 114 insertions(+)
>> create mode 100755 tests/qemu-iotests/110
>> create mode 100644 tests/qemu-iotests/110.out
>>
>> +echo
>> +echo '=== Backing name is always relative to the backed image ==='
>> +echo
>> +
>> +# omit the image size; it shoud work anyway
> s/shoud/should/
As I did the same mistake twice in some other series, I'm beginning to
want to blame my keyboard... (I know that certain key sequences work
bad, for instance, the U in NULL is sometimes omitted (not in null, only
in NULL))
Max
> With the typo fix,
> Reviewed-by: Eric Blake <eblake@redhat.com>
next prev parent reply other threads:[~2014-11-26 9:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-24 9:43 [Qemu-devel] [PATCH v3 0/5] block: Relative backing files Max Reitz
2014-11-24 9:43 ` [Qemu-devel] [PATCH v3 1/5] block: Get full backing filename from string Max Reitz
2014-11-25 19:53 ` Eric Blake
2014-11-26 5:38 ` Fam Zheng
2014-11-24 9:43 ` [Qemu-devel] [PATCH v3 2/5] block: JSON filenames and relative backing files Max Reitz
2014-11-25 19:57 ` Eric Blake
2014-11-26 9:10 ` Max Reitz
2014-11-26 5:35 ` Fam Zheng
2014-11-26 9:12 ` Max Reitz
2014-11-24 9:43 ` [Qemu-devel] [PATCH v3 3/5] block: Relative backing file for image creation Max Reitz
2014-11-25 20:11 ` Eric Blake
2014-11-26 5:40 ` Fam Zheng
2014-11-24 9:43 ` [Qemu-devel] [PATCH v3 4/5] block/vmdk: Relative backing file for creation Max Reitz
2014-11-25 21:52 ` Eric Blake
2014-11-26 5:38 ` Fam Zheng
2014-11-24 9:43 ` [Qemu-devel] [PATCH v3 5/5] iotests: Add test for relative backing file names Max Reitz
2014-11-25 22:06 ` Eric Blake
2014-11-26 9:24 ` Max Reitz [this message]
2014-11-26 5:45 ` Fam Zheng
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=54759C32.1040301@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 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).