qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Fam Zheng <famz@redhat.com>
Cc: qemu-devel@nongnu.org, stefanha@redhat.com, mreitz@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2] qemu-iotests: prefill some data to test image
Date: Wed, 30 Oct 2013 12:51:39 +0100	[thread overview]
Message-ID: <20131030115139.GF2807@dhcp-200-207.str.redhat.com> (raw)
In-Reply-To: <20131030113119.GA5977@T430s.nay.redhat.com>

Am 30.10.2013 um 12:31 hat Fam Zheng geschrieben:
> On Wed, 10/30 12:15, Kevin Wolf wrote:
> > Am 30.10.2013 um 10:42 hat Fam Zheng geschrieben:
> > > Case 030 occasionally fails because of block job compltes too fast to be
> > > captured by script, and 'unexpected qmp event' of job completion causes
> > > the test failure.
> > > 
> > > Simply fill in some data to the test image to make this false alarm less
> > > likely to happen.
> > > 
> > > (For other benefits to prefill data to test image, see also commit
> > > ab68cdfaa).
> > > 
> > > Signed-off-by: Fam Zheng <famz@redhat.com>
> > > 
> > > ---
> > > v2: subsequent to "qemu-iotests: fix 030 for faster machines".
> > > 
> > > Signed-off-by: Fam Zheng <famz@redhat.com>
> > 
> > Did you try using blkdebug to make it deterministic instead of just
> > making failure less likely?
> 
> Yes. blkdebug relies on actual IO, but using images with no data doesn't
> trigger any IO and just completes. Prefilling is the prerequisite to use that.
> This alone already works very well for me, but blkdebug is good to have, too.

That's actually a good point.

> Suspending before starting the block job is obviously the way to do, but
> resuming before cancel_and_wait is not deterministic, either, in the same way.
> We'll need to add cancel_and_resume_and_wait().
> 
> Do you like me to respin or use a follow up patch?

A follow-up patch works for me.

Kevin

  reply	other threads:[~2013-10-30 11:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-30  9:42 [Qemu-devel] [PATCH v2] qemu-iotests: prefill some data to test image Fam Zheng
2013-10-30 11:15 ` Kevin Wolf
2013-10-30 11:31   ` Fam Zheng
2013-10-30 11:51     ` Kevin Wolf [this message]
2013-10-31  2:18 ` [Qemu-devel] [PATCH v3] qemu-iotests: use blkdebug to make test deterministic Fam Zheng
2013-11-06 12:03   ` Stefan Hajnoczi
2013-11-07  7:58     ` Fam Zheng
2013-11-06 12:10   ` Paolo Bonzini
2013-11-07 10:51     ` Fam Zheng
2013-11-07 11:25     ` Fam Zheng
2013-11-07 11:33       ` Paolo Bonzini

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=20131030115139.GF2807@dhcp-200-207.str.redhat.com \
    --to=kwolf@redhat.com \
    --cc=famz@redhat.com \
    --cc=mreitz@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).