Markus Armbruster <arm...@redhat.com> writes: > Fam Zheng <f...@redhat.com> writes: > >> qemu-iotests contains useful tests that have a nice coverage of block layer >> code. Adding check-block (which calls tests/qemu-iotests-quick.sh) to "make >> check" is good for developers' self-testing. >> >> With the first patch, this set takes a half minute on my laptop. If >> "-j" option >> is used, it only takes a few more seconds than what we have now. > > Different data point: elderly machine, spinning rust, /tmp is tmpfs, no > -j: elapsed time increases from ~2 to ~3 minutes.
I'm very much in favour of actually running the tests we have. Running all the block tests for all the formats would be too slow, and that's why you run just the "quick" group, and only for qcow2. Quick enough? Any ideas on speeding it up further? Trimming image sizes, perhaps? What are the slowest tests in the quick group? Why are they slow? How are tests selected for the quick group anyway?
