From: Fam Zheng <famz@redhat.com>
To: John Snow <jsnow@redhat.com>
Cc: kwolf@redhat.com, jcody@redhat.com, qemu-devel@nongnu.org,
qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] iotests: fix race in 030
Date: Mon, 16 Nov 2015 14:49:58 +0800 [thread overview]
Message-ID: <20151116064958.GF20672@ad.usersys.redhat.com> (raw)
In-Reply-To: <1447273656-1748-1-git-send-email-jsnow@redhat.com>
On Wed, 11/11 15:27, John Snow wrote:
> the stop_test case tests that we can resume a block-stream
> command after it has stopped/paused due to error. We cannot
> always reliably query it before it finishes after resume, though,
> so make this a conditional.
>
> The important thing is that we are still testing that it has stopped,
> and that it finishes successfully after we send a resume command.
>
> Signed-off-by: John Snow <jsnow@redhat.com>
> ---
> tests/qemu-iotests/030 | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/tests/qemu-iotests/030 b/tests/qemu-iotests/030
> index 952a524..fd0d186 100755
> --- a/tests/qemu-iotests/030
> +++ b/tests/qemu-iotests/030
> @@ -245,6 +245,7 @@ class TestEIO(TestErrors):
> while not completed:
> for event in self.vm.get_qmp_events(wait=True):
> if event['event'] == 'BLOCK_JOB_ERROR':
> + error = True
> self.assert_qmp(event, 'data/device', 'drive0')
> self.assert_qmp(event, 'data/operation', 'read')
>
> @@ -257,9 +258,11 @@ class TestEIO(TestErrors):
> self.assert_qmp(result, 'return', {})
>
> result = self.vm.qmp('query-block-jobs')
> + if (result == {'return': []}):
Using parenthisis around if conditions is not native Python but "(scalar)"
equals to "scalar", so the statement is still correct. Maybe this could be
fixed when applying, or even if it stays as is:
Reviewed-by: Fam Zheng <famz@redhat.com>
> + # Race; likely already finished. Check.
> + continue
> self.assert_qmp(result, 'return[0]/paused', False)
> self.assert_qmp(result, 'return[0]/io-status', 'ok')
> - error = True
> elif event['event'] == 'BLOCK_JOB_COMPLETED':
> self.assertTrue(error, 'job completed unexpectedly')
> self.assert_qmp(event, 'data/type', 'stream')
> --
> 2.4.3
>
>
next prev parent reply other threads:[~2015-11-16 6:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-11 20:27 [Qemu-devel] [PATCH] iotests: fix race in 030 John Snow
2015-11-11 20:34 ` Jeff Cody
2015-11-12 10:21 ` [Qemu-devel] [Qemu-block] " Alberto Garcia
2015-11-16 6:49 ` Fam Zheng [this message]
2015-11-16 13:43 ` [Qemu-devel] " Kevin Wolf
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=20151116064958.GF20672@ad.usersys.redhat.com \
--to=famz@redhat.com \
--cc=jcody@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@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 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).