diff options
| author | Thomas Huth <thuth@redhat.com> | 2019-08-23 15:35:52 +0200 |
|---|---|---|
| committer | Max Reitz <mreitz@redhat.com> | 2019-09-03 14:56:06 +0200 |
| commit | 21b43d004813ae71d964f74e59ff149bb480db73 (patch) | |
| tree | 5d0ba4794ed8b8e3b8afad5893a97a9ec36d48be /Changelog | |
| parent | 9da126fc2e7c5ab395eac8a5f7c4f119b1434943 (diff) | |
| download | qemu-21b43d004813ae71d964f74e59ff149bb480db73.zip qemu-21b43d004813ae71d964f74e59ff149bb480db73.tar.gz qemu-21b43d004813ae71d964f74e59ff149bb480db73.tar.bz2 | |
iotests: Check for enabled drivers before testing them
It is possible to enable only a subset of the block drivers with the
"--block-drv-rw-whitelist" option of the "configure" script. All other
drivers are marked as unusable (or only included as read-only with the
"--block-drv-ro-whitelist" option). If an iotest is now using such a
disabled block driver, it is failing - which is bad, since at least the
tests in the "auto" group should be able to deal with this situation.
Thus let's introduce a "_require_drivers" function that can be used by
the shell tests to check for the availability of certain drivers first,
and marks the test as "not run" if one of the drivers is missing.
This patch mainly targets the test in the "auto" group which should
never fail in such a case, but also improves some of the other tests
along the way. Note that we also assume that the "qcow2" and "file"
drivers are always available - otherwise it does not make sense to
run "make check-block" at all (which only tests with qcow2 by default).
Signed-off-by: Thomas Huth <thuth@redhat.com>
Message-id: 20190823133552.11680-1-thuth@redhat.com
Signed-off-by: Max Reitz <mreitz@redhat.com>
Diffstat (limited to 'Changelog')
0 files changed, 0 insertions, 0 deletions