[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v2 5/8] iotests/129: Use throttle node
From: |
Eric Blake |
Subject: |
Re: [PATCH v2 5/8] iotests/129: Use throttle node |
Date: |
Wed, 13 Jan 2021 13:02:58 -0600 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0 |
On 1/13/21 11:57 AM, Max Reitz wrote:
> Throttling on the BB has not affected block jobs in a while, so it is
> possible that one of the jobs in 129 finishes before the VM is stopped.
> We can fix that by running the job from a throttle node.
>
> Signed-off-by: Max Reitz <mreitz@redhat.com>
> ---
> tests/qemu-iotests/129 | 37 +++++++++++++------------------------
> 1 file changed, 13 insertions(+), 24 deletions(-)
>
Reviewed-by: Eric Blake <eblake@redhat.com>
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
[PATCH v2 2/8] iotests: Move try_remove to iotests.py, Max Reitz, 2021/01/13
[PATCH v2 3/8] iotests/129: Remove test images in tearDown(), Max Reitz, 2021/01/13
[PATCH v2 4/8] iotests/129: Do not check @busy, Max Reitz, 2021/01/13
[PATCH v2 6/8] iotests/129: Actually test a commit job, Max Reitz, 2021/01/13
[PATCH v2 7/8] iotests/129: Limit mirror job's buffer size, Max Reitz, 2021/01/13
[PATCH v2 5/8] iotests/129: Use throttle node, Max Reitz, 2021/01/13
[PATCH v2 8/8] iotests/129: Clean up pylint and mypy complaints, Max Reitz, 2021/01/13