From: Peter Xu <peterx@redhat.com>
To: Fabiano Rosas <farosas@suse.de>
Cc: qemu-devel@nongnu.org,
"Daniel P . Berrangé" <berrange@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Thomas Huth" <thuth@redhat.com>,
"Laurent Vivier" <lvivier@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: [PATCH v3 4/4] [NOT FOR MERGE] tests/qtest/migration: Adapt tests to use older QEMUs
Date: Wed, 10 Jan 2024 12:08:27 +0800 [thread overview]
Message-ID: <ZZ4YOw6Cy5EYo_f4@x1n> (raw)
In-Reply-To: <87zfxe7eev.fsf@suse.de>
On Tue, Jan 09, 2024 at 11:46:32AM -0300, Fabiano Rosas wrote:
> Hm, it would be better to avoid the extra maintenance task at the start
> of every release, no? It also blocks us from doing n-2 even
> experimentally.
See my other reply, on whether we can use "n-1" for migration-test. If
that can work for us, then IIUC we can avoid either "since:" or any
relevant flag, neither do we need to unmask tests after each releases. All
old tests should always "just work" with a new qemu binary.
One drawback I can think of is, new tests (even if applicable to old qemu
binaries) will only start to take effect on cross-binary test until the
next release, but that's not so bad I assume.
Since the QTEST_QEMU_BINARY_SRC|DST function is already merged in 8.2, I
think we can already start kicking them and enable them for 9.0 if it works.
--
Peter Xu
next prev parent reply other threads:[~2024-01-10 4:08 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-05 18:04 [PATCH v3 0/4] migration & CI: Add a CI job for migration compat testing Fabiano Rosas
2024-01-05 18:04 ` [PATCH v3 1/4] tests/qtest: Add a helper to query the QEMU version Fabiano Rosas
2024-01-08 8:13 ` Peter Xu
2024-01-05 18:04 ` [PATCH v3 2/4] tests/qtest/migration: Add infrastructure to skip tests on older QEMUs Fabiano Rosas
2024-01-08 8:13 ` Peter Xu
2024-01-08 8:39 ` Peter Xu
2024-01-08 14:49 ` Fabiano Rosas
2024-01-09 2:26 ` Peter Xu
2024-01-09 16:50 ` Fabiano Rosas
2024-01-08 14:57 ` Daniel P. Berrangé
2024-01-05 18:04 ` [PATCH v3 3/4] ci: Add a migration compatibility test job Fabiano Rosas
2024-01-09 7:14 ` Peter Xu
2024-01-09 13:00 ` Fabiano Rosas
2024-01-10 3:58 ` Peter Xu
2024-01-09 18:15 ` Cédric Le Goater
2024-01-09 20:58 ` Fabiano Rosas
2024-01-10 10:30 ` Thomas Huth
2024-01-05 18:04 ` [PATCH v3 4/4] [NOT FOR MERGE] tests/qtest/migration: Adapt tests to use older QEMUs Fabiano Rosas
2024-01-08 8:15 ` Peter Xu
2024-01-08 15:37 ` Fabiano Rosas
2024-01-09 3:51 ` Peter Xu
2024-01-09 14:46 ` Fabiano Rosas
2024-01-10 4:08 ` Peter Xu [this message]
2024-01-10 14:42 ` Fabiano Rosas
2024-01-11 2:35 ` Peter Xu
2024-01-11 13:58 ` Fabiano Rosas
2024-01-15 4:13 ` Peter Xu
2024-01-15 13:45 ` Fabiano Rosas
2024-01-15 23:28 ` Peter Xu
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=ZZ4YOw6Cy5EYo_f4@x1n \
--to=peterx@redhat.com \
--cc=berrange@redhat.com \
--cc=farosas@suse.de \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--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).