From: Kevin Wolf <kwolf@redhat.com>
To: John Snow <jsnow@redhat.com>
Cc: qemu-devel@nongnu.org,
"open list:Block layer core" <qemu-block@nongnu.org>
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH] qemu-iotests: Reduce racy output in 028
Date: Tue, 19 Jan 2016 17:15:04 +0100 [thread overview]
Message-ID: <20160119161504.GC4579@noname.redhat.com> (raw)
In-Reply-To: <56747F60.8030000@redhat.com>
Am 18.12.2015 um 22:49 hat John Snow geschrieben:
>
>
> On 12/18/2015 03:46 PM, Eric Blake wrote:
> > On 12/11/2015 06:23 PM, John Snow wrote:
> >> On 12/10/2015 10:27 PM, Eric Blake wrote:
> >>> On my machine, './check -qcow2 028' was failing about 80% of the
> >>> time, due to a race in how many times the repeated attempts
> >>> to run 'info block-jobs' could occur before the job was done,
> >>> showing up as a failure of fewer '(qemu) ' prompts than in the
> >>> expected output. Silence the output during the repetitions, then
> >>> add a final clean command to keep the expected output useful;
> >>> once patched, I was finally able to run the test 20 times in a
> >>> row with no failures.
> It looks sane to me, because you are deleting the insane portion of the
> expected output. The final "info block" command serves as an assertion
> that the loop polled successfully.
>
> Reviewed-by: John Snow <jsnow@redhat.com>
Thanks, applied to the block branch.
Kevin
prev parent reply other threads:[~2016-01-19 16:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-11 3:27 [Qemu-devel] [PATCH for-2.5?] qemu-iotests: Reduce racy output in 028 Eric Blake
2015-12-11 13:22 ` Peter Maydell
2015-12-12 1:23 ` [Qemu-devel] [Qemu-block] " John Snow
2015-12-18 20:46 ` [Qemu-devel] [Qemu-block] [PATCH] " Eric Blake
2015-12-18 21:49 ` John Snow
2016-01-19 16:15 ` Kevin Wolf [this message]
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=20160119161504.GC4579@noname.redhat.com \
--to=kwolf@redhat.com \
--cc=jsnow@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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.