| commit | f9a6256b48f29c2816f6119c17b80b0e93d76c42 | |
| author | Max Reitz <mreitz@redhat.com> | |
| Mon, 18 Jan 2021 10:57:15 +0000 (18 11:57 +0100) | ||
| committer | Max Reitz <mreitz@redhat.com> | |
| Tue, 26 Jan 2021 13:36:37 +0000 (26 14:36 +0100) | ||
| tree | 11fd7c67f3146d10a6b033ce6327a2d9b203bb02 | treesnapshot (tar.gz zip) |
| parent | 20e2580eec0f9bb7789fe545a4d57da7ab8c2be8 | commitdiff |
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>
@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>
| tests/qemu-iotests/129 | diffblobblamehistory |