From: Fabiano Rosas <farosas@suse.de>
To: qemu-devel@nongnu.org
Cc: "Juan Quintela" <quintela@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Daniel P . Berrangé" <berrange@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: [RFC PATCH 0/2] tests/qtest: Run migration subtests via meson
Date: Mon, 3 Jul 2023 11:46:58 -0300 [thread overview]
Message-ID: <20230703144700.13536-1-farosas@suse.de> (raw)
We've had some issues with the migration-test failing in CI and giving
no clue as to which migration sub-test has failed. I think it would be
an improvement to have each subtest listed individually.
With this we can see which migration test has failed, can set timeouts
individually and can run 'make check-migration' to run only the
migration tests.
It does however increase the amount of lines emitted with make check,
so let me know if this is an issue.
I had to include some hacking due to meson, but I think it is simple
enough and worth the benefits.
CI run: https://gitlab.com/farosas/qemu/-/pipelines/919324510
Fabiano Rosas (2):
tests/qtest: Add a script to gather migration tests list
tests/qtest: Pass migration tests individually to meson
.gitlab-ci.d/windows.yml | 2 +-
tests/qtest/gen_migration_tests_list.py | 12 ++++++++
tests/qtest/meson.build | 40 +++++++++++++++++++------
3 files changed, 44 insertions(+), 10 deletions(-)
create mode 100644 tests/qtest/gen_migration_tests_list.py
--
2.35.3
next reply other threads:[~2023-07-03 14:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 14:46 Fabiano Rosas [this message]
2023-07-03 14:46 ` [RFC PATCH 1/2] tests/qtest: Add a script to gather migration tests list Fabiano Rosas
2023-07-03 14:47 ` [RFC PATCH 2/2] tests/qtest: Pass migration tests individually to meson Fabiano Rosas
2023-07-03 15:17 ` [RFC PATCH 0/2] tests/qtest: Run migration subtests via meson Daniel P. Berrangé
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230703144700.13536-1-farosas@suse.de \
--to=farosas@suse.de \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=thuth@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).