From: Max Reitz <mreitz@redhat.com>
To: Max Reitz <mreitz@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>, Fam Zheng <famz@redhat.com>,
qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v6 5/6] qemu-iotests: Discard specific info in _img_info
Date: Tue, 01 Oct 2013 14:47:17 +0200 [thread overview]
Message-ID: <524AC455.9060609@redhat.com> (raw)
In-Reply-To: <1380630722-19430-6-git-send-email-mreitz@redhat.com>
On 2013-10-01 14:32, Max Reitz wrote:
> In _img_info, filter out additional information specific to the image
> format provided by qemu-img info, since tests designed for multiple
> image formats would produce different outputs for every image format
> otherwise.
>
> Signed-off-by: Max Reitz <mreitz@redhat.com>
Ah, I just noticed I forgot to include a sample of what is to be
stripped away, so this will have to do for now:
All existing tests using qemu-img info rely on it not emitting image
format specific information. Therefore, this data has to be stripped away.
In a human-readable dump, that information will always be last for each
"image information block" (multiple blocks are emitted when looking at
the backing file chain). Every block is seperated by an empty line.
Therefore, in this case, everything starting with the line "Format
specific information:" up to that empty line (or EOF, if it's the last
block) has to be stripped.
The JSON dump will always emit "pretty" JSON data. Therefore, the ending
brace of every object will be indented as much as the object itself is
(and every line in between has more indentation). Thus, in this case, we
have to strip all the data beginning with ' *"format-specific": {' until
a line ' *},' appears which is indented just as much as the former was.
Hm, now that I think of it… Actually, the ending line is rather ' *},?',
since the comma is "optional", depending on whether it is the last
object or not. Well, I think this calls for v7, then. I'll include this
description in patch v7 5/6.
Max
next prev parent reply other threads:[~2013-10-01 12:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-01 12:31 [Qemu-devel] [PATCH v6 0/6] Provide additional info through qemu-img info Max Reitz
2013-10-01 12:31 ` [Qemu-devel] [PATCH v6 1/6] qapi: Add ImageInfoSpecific type Max Reitz
2013-10-01 12:31 ` [Qemu-devel] [PATCH v6 2/6] block: Add bdrv_get_specific_info Max Reitz
2013-10-01 12:31 ` [Qemu-devel] [PATCH v6 3/6] block/qapi: Human-readable ImageInfoSpecific dump Max Reitz
2013-10-01 12:32 ` [Qemu-devel] [PATCH v6 4/6] qcow2: Add support for ImageInfoSpecific Max Reitz
2013-10-01 12:32 ` [Qemu-devel] [PATCH v6 5/6] qemu-iotests: Discard specific info in _img_info Max Reitz
2013-10-01 12:47 ` Max Reitz [this message]
2013-10-01 12:32 ` [Qemu-devel] [PATCH v6 6/6] qemu-iotests: Additional info from qemu-img info Max Reitz
2013-10-01 12:50 ` [Qemu-devel] [PATCH v6 0/6] Provide additional info through " Eric Blake
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=524AC455.9060609@redhat.com \
--to=mreitz@redhat.com \
--cc=famz@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).