diff options
| author | Daniel P. Berrangé <berrange@redhat.com> | 2023-03-15 17:43:23 +0000 |
|---|---|---|
| committer | Alex Bennée <alex.bennee@linaro.org> | 2023-03-22 15:08:26 +0000 |
| commit | 51ab5f8bd795d8980351f8531e54995ff9e6d163 (patch) | |
| tree | 2dd56f7758aac59c534383df55295ae668e7f367 /scripts/qapi/commands.py | |
| parent | 5ba7db0938c8b8e6e457b9aab8c6c625913d773f (diff) | |
| download | qemu-51ab5f8bd795d8980351f8531e54995ff9e6d163.zip qemu-51ab5f8bd795d8980351f8531e54995ff9e6d163.tar.gz qemu-51ab5f8bd795d8980351f8531e54995ff9e6d163.tar.bz2 | |
iotests: register each I/O test separately with meson
Currently meson registers a single test that invokes an entire group of
I/O tests, hiding the test granularity from meson. There are various
downsides of doing this
* You cannot ask 'meson test' to invoke a single I/O test
* The meson test timeout can't be applied to the individual
tests
* Meson only gets a pass/fail for the overall I/O test group
not individual tests
* If a CI job gets killed by the GitLab timeout, we don't
get visibility into how far through the I/O tests
execution got.
This switches meson to perform test discovery by invoking 'check' in
dry-run mode. It then registers one meson test case for each I/O
test. Parallel execution remains disabled since the I/O tests do not
use self contained execution environments and thus conflict with
each other.
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
Reviewed-by: Thomas Huth <thuth@redhat.com>
Acked-by: Hanna Czenczek <hreitz@redhat.com>
Tested-by: Thomas Huth <thuth@redhat.com>
Message-Id: <20230303160727.3977246-8-berrange@redhat.com>
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Message-Id: <20230315174331.2959-25-alex.bennee@linaro.org>
Diffstat (limited to 'scripts/qapi/commands.py')
0 files changed, 0 insertions, 0 deletions