From: Thomas Huth <thuth@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>, qemu-devel@nongnu.org
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Beraldo Leal" <bleal@redhat.com>
Subject: Re: [PATCH] ci: replace x86_64 macos-11 with aarch64 macos-12
Date: Thu, 17 Nov 2022 09:57:10 +0100 [thread overview]
Message-ID: <4baeb599-43df-34cd-0ae1-5f2454b7069d@redhat.com> (raw)
In-Reply-To: <20221116175023.80627-1-berrange@redhat.com>
On 16/11/2022 18.50, Daniel P. Berrangé wrote:
> The Cirrus CI service has announced the intent to discontinue
> support for x86_64 macOS CI runners. They already have aarch64
> runners available and require all projects to switch to these
> images before Jan 1st 2023. The different architecture is
> merely determined by the image name requested.
>
> For aarch64 they only support macOS 12 onwards. At the same
> time our support policy only guarantees the most recent 2
> major versions, so macOS 12 is already technically our min
> version.
>
> https://cirrus-ci.org/blog/2022/11/08/sunsetting-intel-macos-instances/
> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
> ---
> .gitlab-ci.d/cirrus.yml | 12 ++++++------
> .gitlab-ci.d/cirrus/{macos-11.vars => macos-12.vars} | 12 ++++++------
> tests/lcitool/libvirt-ci | 2 +-
> tests/lcitool/refresh | 2 +-
> 4 files changed, 14 insertions(+), 14 deletions(-)
> rename .gitlab-ci.d/cirrus/{macos-11.vars => macos-12.vars} (74%)
Works for me:
https://gitlab.com/thuth/qemu/-/jobs/3336969845
Tested-by: Thomas Huth <thuth@redhat.com>
I can pick this up for my next pull request.
next prev parent reply other threads:[~2022-11-17 8:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 17:50 [PATCH] ci: replace x86_64 macos-11 with aarch64 macos-12 Daniel P. Berrangé
2022-11-17 8:57 ` Thomas Huth [this message]
2022-11-17 17:21 ` Alex Bennée
2022-11-17 14:39 ` Philippe Mathieu-Daudé
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=4baeb599-43df-34cd-0ae1-5f2454b7069d@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=bleal@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=wainersm@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).