On Thu, Jul 20, 2017 at 11:47:27PM -0400, Cleber Rosa wrote: > This is a follow up to a previous discussion about reported failures when > running some qemu-iotests. Turns out the failures were due to missing > libraries, which in turn, reflected on the host build configuration. > > This series introduces a tool that can check both host and target level > build configurations. On top of that, it adds a function to to be used > on qemu-iotests. Finally, as an example, it sets a test to be skipped > if the required feature is not enable on the host build configuration. > > Cleber Rosa (3): > scripts: introduce buildconf.py > qemu-iotests: add _require_feature() function > qemu-iotests: require CONFIG_LINUX_AIO for test 087 > > scripts/buildconf.py | 278 > +++++++++++++++++++++++++++++++++++++++++++ > tests/qemu-iotests/087 | 1 + > tests/qemu-iotests/check | 2 + > tests/qemu-iotests/common.rc | 7 ++ > 4 files changed, 288 insertions(+) >
It should be possible to run iotests against any qemu/qemu-img/qemu-io/qemu-nbd binaries - even if no build root is available. How about invoking qemu-img and tools to determine their capabilities? At the beginning of ./check, query the qemu/qemu-img/qemu-io/qemu-nbd binaries for specific features. This produces a set of available features and tests can say: _supported_feature aio_native This feature can be checked by opening an image file: qemu-io --format raw --nocache --native-aio --cmd quit test.img
signature.asc
Description: PGP signature
