qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: qemu-devel@nongnu.org, kwolf@redhat.com, jsnow@redhat.com,
	jcody@redhat.com, qemu-block@nongnu.org,
	Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 5/5] iotests: Add test 197 for covering copy-on-read
Date: Thu, 5 Oct 2017 09:44:36 -0500	[thread overview]
Message-ID: <36585356-7cb7-30c7-bfe4-db6a56796b1d@redhat.com> (raw)
In-Reply-To: <20171005144119.GG10969@stefanha-x1.localdomain>

[-- Attachment #1: Type: text/plain, Size: 1674 bytes --]

On 10/05/2017 09:41 AM, Stefan Hajnoczi wrote:
> On Tue, Oct 03, 2017 at 08:43:47PM -0500, Eric Blake wrote:
>> Add a test for qcow2 copy-on-read behavior, including exposure
>> for the just-fixed bugs.
>>
>> The copy-on-read behavior is always to a qcow2 image, but the
>> test is careful to allow running with most image protocol/format
>> combos as the backing file being copied from (luks being the
>> exception, as it is harder to pass the right secret to all the
>> right places).  In fact, for './check nbd', this appears to be
>> the first time we've had a qcow2 image wrapping NBD, requiring
>> an additional line in _filter_img_create to match the similar
>> line in _filter_img_info.
>>
>> Invoking blkdebug to prove we don't write too much took some
>> effort to get working; and it requires that $TEST_WRAP (based
>> on $TEST_DIR) not be subject to word splitting.  We may decide
>> later to have the entire iotests suite use relative rather than
>> absolute names, to avoid problems inherited by the absolute
>> name of $PWD or $TEST_DIR, at which point the sanity check in
>> this commit could be simplified.
>>
>> Signed-off-by: Eric Blake <eblake@redhat.com>
>>

> 
> Aside from the 2GB request issue:

I'm wondering if it is easy enough to just capture the qemu-io output
into a temporary holding area, grep that for success or OOM, then skip
the test on OOM (for small machines) or log the success (for beefy
spots), so that at least the test will not hold up CI efforts on small
machines.

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3266
Virtualization:  qemu.org | libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 619 bytes --]

  reply	other threads:[~2017-10-05 14:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-04  1:43 [Qemu-devel] [PATCH v2 0/5] block: Avoid copy-on-read assertions Eric Blake
2017-10-04  1:43 ` [Qemu-devel] [PATCH v2 1/5] qemu-io: Add -C for opening with copy-on-read Eric Blake
2017-10-04  1:43 ` [Qemu-devel] [PATCH v2 2/5] block: Uniform handling of 0-length bdrv_get_block_status() Eric Blake
2017-10-05 14:35   ` Stefan Hajnoczi
2017-10-05 14:41     ` Eric Blake
2017-10-04  1:43 ` [Qemu-devel] [PATCH v2 3/5] block: Add blkdebug hook for copy-on-read Eric Blake
2017-10-04  1:43 ` [Qemu-devel] [PATCH v2 4/5] block: Perform copy-on-read in loop Eric Blake
2017-10-05 14:55   ` Kevin Wolf
2017-10-05 15:36   ` Stefan Hajnoczi
2017-10-04  1:43 ` [Qemu-devel] [PATCH v2 5/5] iotests: Add test 197 for covering copy-on-read Eric Blake
2017-10-05 14:41   ` Stefan Hajnoczi
2017-10-05 14:44     ` Eric Blake [this message]
2017-10-05 14:47       ` Eric Blake
2017-10-04  2:16 ` [Qemu-devel] [PATCH v2 0/5] block: Avoid copy-on-read assertions no-reply
2017-10-04  2:22   ` Eric Blake
2017-10-04  5:39     ` 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=36585356-7cb7-30c7-bfe4-db6a56796b1d@redhat.com \
    --to=eblake@redhat.com \
    --cc=jcody@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --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).