From: peterx@redhat.com
To: qemu-devel@nongnu.org
Cc: "Daniel P . Berrangé" <berrange@redhat.com>,
"Fabiano Rosas" <farosas@suse.de>,
peterx@redhat.com, "Peter Maydell" <peter.maydell@linaro.org>,
"Eric Auger" <eric.auger@redhat.com>,
"Sebastian Ott" <sebott@redhat.com>
Subject: [PATCH 0/3] ci: Fixes on the recent cross-binary test case
Date: Tue, 6 Feb 2024 14:31:48 +0800 [thread overview]
Message-ID: <20240206063151.215986-1-peterx@redhat.com> (raw)
From: Peter Xu <peterx@redhat.com>
Hi,
This small patchset updates the recent cross-binary test for migration on
a few things.
Patch 1 modifies the aarch64 test GIC version to 3 rather than "max",
paving way for enabling it, even if the CPU model is not yet ready.
Patch 2 removes the tag dependency of the new build-previous-qemu job, so
that in personal CI pipelines the job won't fail if the tag is missing, as
reported by Peter Maydell, and solution suggested by Dan.
Patch 3 updates the comment for aarch64 on the test to state the fact, and
what is missing. Then we don't target it support for v9.0, but only until
we have a stable CPU model for aarch64 (if ever possible to support both
tcg and kvm).
Comments welcomed, thanks.
Peter Xu (3):
tests/migration-test: Stick with gicv3 in aarch64 test
ci: Remove tag dependency for build-previous-qemu
ci: Update comment for migration-compat-aarch64
tests/qtest/migration-test.c | 2 +-
.gitlab-ci.d/buildtest.yml | 9 ++++++---
2 files changed, 7 insertions(+), 4 deletions(-)
--
2.43.0
next reply other threads:[~2024-02-06 6:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 6:31 peterx [this message]
2024-02-06 6:31 ` [PATCH 1/3] tests/migration-test: Stick with gicv3 in aarch64 test peterx
2024-02-06 8:13 ` Daniel P. Berrangé
2024-02-06 6:31 ` [PATCH 2/3] ci: Remove tag dependency for build-previous-qemu peterx
2024-02-06 8:11 ` Daniel P. Berrangé
2024-02-06 8:30 ` Peter Xu
2024-02-06 6:31 ` [PATCH 3/3] ci: Update comment for migration-compat-aarch64 peterx
2024-02-06 8:12 ` 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=20240206063151.215986-1-peterx@redhat.com \
--to=peterx@redhat.com \
--cc=berrange@redhat.com \
--cc=eric.auger@redhat.com \
--cc=farosas@suse.de \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=sebott@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.