From: Eric Blake <eblake@redhat.com>
To: Hanna Reitz <hreitz@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel@nongnu.org, qemu-block@nongnu.org
Subject: Re: [PATCH v2 4/4] iotests/185: Add post-READY quit tests
Date: Thu, 3 Mar 2022 16:36:21 -0600 [thread overview]
Message-ID: <20220303223621.pv4zhtiu6rwderdn@redhat.com> (raw)
In-Reply-To: <20220303164814.284974-5-hreitz@redhat.com>
On Thu, Mar 03, 2022 at 05:48:14PM +0100, Hanna Reitz wrote:
> 185 tests quitting qemu while a block job is active. It does not
> specifically test quitting qemu while a mirror or active commit job is
> in its READY phase.
>
> Add two test cases for this, where we respectively mirror or commit to
> an external QSD instance, which provides a throttled block device. qemu
> is supposed to cancel the job so that it can quit as soon as possible
> instead of waiting for the job to complete (which it did before 6.2).
>
> Signed-off-by: Hanna Reitz <hreitz@redhat.com>
> ---
> tests/qemu-iotests/185 | 190 ++++++++++++++++++++++++++++++++++++-
> tests/qemu-iotests/185.out | 48 ++++++++++
> 2 files changed, 237 insertions(+), 1 deletion(-)
>
> diff --git a/tests/qemu-iotests/185 b/tests/qemu-iotests/185
> index f2ec5c5ceb..8b1143dc16 100755
> --- a/tests/qemu-iotests/185
> +++ b/tests/qemu-iotests/185
> @@ -33,6 +33,12 @@ _cleanup()
> _rm_test_img "${TEST_IMG}.copy"
> _cleanup_test_img
> _cleanup_qemu
> +
> + if [ -f "$TEST_DIR/qsd.pid" ]; then
> + kill -SIGKILL "$(cat "$TEST_DIR/qsd.pid")"
> + rm -f "$TEST_DIR/qsd.pid"
> + fi
> + rm -f "$SOCK_DIR/qsd.sock"
> }
> trap "_cleanup; exit \$status" 0 1 2 3 15
>
> @@ -45,7 +51,7 @@ _supported_fmt qcow2
> _supported_proto file
> _supported_os Linux
>
> -size=64M
> +size=$((64 * 1048576))
I tend to write $((64 * 1024 * 1024)) rather than remembering all the
digits of 2^20, but your way is fine.
Nice test addition!
Reviewed-by: Eric Blake <eblake@redhat.com>
I'm happy to queue this series through my NBD tree in time for
softfreeze, if no one else speaks for it first.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2022-03-03 22:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-03 16:48 [PATCH v2 0/4] qsd: Add --daemonize; and add job quit tests Hanna Reitz
2022-03-03 16:48 ` [PATCH v2 1/4] os-posix: Add os_set_daemonize() Hanna Reitz
2022-03-03 20:22 ` Eric Blake
2022-03-04 9:19 ` Daniel P. Berrangé
2022-03-04 10:20 ` Kevin Wolf
2022-03-04 11:58 ` Daniel P. Berrangé
2022-03-03 16:48 ` [PATCH v2 2/4] qsd: Add pre-init argument parsing pass Hanna Reitz
2022-03-03 22:27 ` Eric Blake
2022-03-03 16:48 ` [PATCH v2 3/4] qsd: Add --daemonize Hanna Reitz
2022-03-03 22:31 ` Eric Blake
2022-03-04 9:27 ` Kevin Wolf
2022-03-03 16:48 ` [PATCH v2 4/4] iotests/185: Add post-READY quit tests Hanna Reitz
2022-03-03 22:36 ` Eric Blake [this message]
2022-03-04 10:47 ` [PATCH v2 0/4] qsd: Add --daemonize; and add job " 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=20220303223621.pv4zhtiu6rwderdn@redhat.com \
--to=eblake@redhat.com \
--cc=hreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@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).