From: Max Reitz <mreitz@redhat.com>
To: qemu-block@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
John Snow <jsnow@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [PATCH v2 3/3] iotests/041: block-job-complete on user-paused job
Date: Fri, 9 Apr 2021 15:45:11 +0200 [thread overview]
Message-ID: <93dc20cf-0ae0-40c1-e0d4-502a351f407a@redhat.com> (raw)
In-Reply-To: <20210409132948.195511-4-mreitz@redhat.com>
On 09.04.21 15:29, Max Reitz wrote:
> Expand test_pause() to check what happens when issuing
> block-job-complete on a job that is on STANDBY because it has been
> paused by the user. (This should be an error, and in particular not
> hang job_wait_unpaused().)
>
> Signed-off-by: Max Reitz <mreitz@redhat.com>
> ---
> tests/qemu-iotests/041 | 13 ++++++++++++-
> 1 file changed, 12 insertions(+), 1 deletion(-)
>
> diff --git a/tests/qemu-iotests/041 b/tests/qemu-iotests/041
> index 5cc02b24fc..d2c9669741 100755
> --- a/tests/qemu-iotests/041
> +++ b/tests/qemu-iotests/041
> @@ -120,7 +120,18 @@ class TestSingleDrive(iotests.QMPTestCase):
> result = self.vm.qmp('block-job-resume', device='drive0')
> self.assert_qmp(result, 'return', {})
>
> - self.complete_and_wait()
> + self.wait_ready()
> +
> + # Check that a job on STANDBY cannot be completed
> + self.pause_job('drive0')
> + result = self.vm.qmp('block-job-complete', device='drive0')
> + self.assert_qmp(result, 'error/desc',
> + "Job 'drive0' has been paused by the user")
Oops. Should now be
"Job 'drive0' has been paused and needs to be explicitly resumed"
of course.
Max
> +
> + result = self.vm.qmp('block-job-resume', device='drive0')
> + self.assert_qmp(result, 'return', {})
> +
> + self.complete_and_wait(wait_ready=False)
> self.vm.shutdown()
> self.assertTrue(iotests.compare_images(test_img, target_img),
> 'target image does not match source after mirroring')
>
next prev parent reply other threads:[~2021-04-09 13:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-09 13:29 [PATCH v2 0/3] job: Add job_wait_unpaused() for block-job-complete Max Reitz
2021-04-09 13:29 ` [PATCH v2 1/3] " Max Reitz
2021-04-09 13:29 ` [PATCH v2 2/3] test-blockjob: Test job_wait_unpaused() Max Reitz
2021-04-09 13:29 ` [PATCH v2 3/3] iotests/041: block-job-complete on user-paused job Max Reitz
2021-04-09 13:45 ` Max Reitz [this message]
2021-04-09 13:29 ` [PATCH v2 4/3] iotests: Test completion immediately after drain Max Reitz
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=93dc20cf-0ae0-40c1-e0d4-502a351f407a@redhat.com \
--to=mreitz@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.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).