summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMax Reitz2021-01-18 11:57:15 +0100
committerMax Reitz2021-01-26 14:36:37 +0100
commitf9a6256b48f29c2816f6119c17b80b0e93d76c42 (patch)
tree11fd7c67f3146d10a6b033ce6327a2d9b203bb02
parentiotests/129: Remove test images in tearDown() (diff)
downloadqemu-f9a6256b48f29c2816f6119c17b80b0e93d76c42.tar.gz
qemu-f9a6256b48f29c2816f6119c17b80b0e93d76c42.tar.xz
qemu-f9a6256b48f29c2816f6119c17b80b0e93d76c42.zip
iotests/129: Do not check @busy
@busy is false when the job is paused, which happens all the time because that is how jobs yield (e.g. for mirror at least since commit 565ac01f8d3). Back when 129 was added (2015), perhaps there was no better way of checking whether the job was still actually running. Now we have the @status field (as of 58b295ba52c, i.e. 2018), which can give us exactly that information. Signed-off-by: Max Reitz <mreitz@redhat.com> Reviewed-by: Eric Blake <eblake@redhat.com> Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com> Reviewed-by: Willian Rampazzo <willianr@redhat.com> Message-Id: <20210118105720.14824-6-mreitz@redhat.com>
-rwxr-xr-xtests/qemu-iotests/1292
1 files changed, 1 insertions, 1 deletions
diff --git a/tests/qemu-iotests/129 b/tests/qemu-iotests/129
index bd29c54af8..0f2e5418ef 100755
--- a/tests/qemu-iotests/129
+++ b/tests/qemu-iotests/129
@@ -70,7 +70,7 @@ class TestStopWithBlockJob(iotests.QMPTestCase):
result = self.vm.qmp("stop")
self.assert_qmp(result, 'return', {})
result = self.vm.qmp("query-block-jobs")
- self.assert_qmp(result, 'return[0]/busy', True)
+ self.assert_qmp(result, 'return[0]/status', 'running')
self.assert_qmp(result, 'return[0]/ready', False)
def test_drive_mirror(self):