| commit | cd2058289bbe0437c2818f69a8c25a7618e906bd | |
| author | Thomas Huth <thuth@redhat.com> | |
| Tue, 21 Jan 2020 09:52:04 +0000 (21 10:52 +0100) | ||
| committer | Max Reitz <mreitz@redhat.com> | |
| Thu, 6 Feb 2020 12:47:45 +0000 (6 13:47 +0100) | ||
| tree | 6e6cc98eef60047252c6ae60e596e13414a5bfb7 | treesnapshot (tar.gz zip) |
| parent | 9bdabfbe722e4d47892dfea17ae4c1670e54123b | commitdiff |
iotests: Skip Python-based tests if QEMU does not support virtio-blk
We are going to enable some of the python-based tests in the "auto" group,
and these tests require virtio-blk to work properly. Running iotests
without virtio-blk likely does not make too much sense anyway, so instead
of adding a check for the availability of virtio-blk to each and every
test (which does not sound very appealing), let's rather add a check for
this a central spot in the "check" script instead (so that it is still
possible to run "make check" for qemu-system-tricore for example).
Signed-off-by: Thomas Huth <thuth@redhat.com>
Message-id: 20200121095205.26323-6-thuth@redhat.com
Signed-off-by: Max Reitz <mreitz@redhat.com>
We are going to enable some of the python-based tests in the "auto" group,
and these tests require virtio-blk to work properly. Running iotests
without virtio-blk likely does not make too much sense anyway, so instead
of adding a check for the availability of virtio-blk to each and every
test (which does not sound very appealing), let's rather add a check for
this a central spot in the "check" script instead (so that it is still
possible to run "make check" for qemu-system-tricore for example).
Signed-off-by: Thomas Huth <thuth@redhat.com>
Message-id: 20200121095205.26323-6-thuth@redhat.com
Signed-off-by: Max Reitz <mreitz@redhat.com>
| tests/qemu-iotests/check | diffblobblamehistory |