From: Patrick Steinhardt <ps@pks.im>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] github-ci: update macos jobs to macos-15
Date: Mon, 19 Oct 2026 09:12:55 +0200 [thread overview]
Message-ID: <atXC91tL7MHRioPZ@pks.im> (raw)
In-Reply-To: <xmqqfqy5clgz.fsf@gitster.g>
On Fri, Oct 16, 2026 at 03:46:36PM -0700, Junio C Hamano wrote:
> diff --git i/.github/workflows/main.yml w/.github/workflows/main.yml
> index b229739be8..d69f6f2b10 100644
> --- i/.github/workflows/main.yml
> +++ w/.github/workflows/main.yml
> @@ -349,16 +349,16 @@ jobs:
> vector:
> - jobname: osx-clang
> cc: clang
> - pool: macos-14
> + pool: macos-15
> - jobname: osx-reftable
> cc: clang
> - pool: macos-14
> + pool: macos-15
> - jobname: osx-gcc
> cc: gcc-13
> - pool: macos-14
> + pool: macos-15
> - jobname: osx-meson
> cc: clang
> - pool: macos-14
> + pool: macos-15
Do we maybe want to update those jobs to use a mixture of macos-15 and
macos-26? In GitLab CI we use macos-15 for osx-clang and macos-26 for
everything else. Like that we have higher test coverage compared to only
exercising one major release.
Patrick
next prev parent reply other threads:[~2026-10-19 7:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 22:46 [PATCH] github-ci: update macos jobs to macos-15 Junio C Hamano
2026-10-17 13:36 ` brian m. carlson
2026-10-19 7:12 ` Patrick Steinhardt [this message]
2026-10-19 18:00 ` Junio C Hamano
2026-10-19 19:41 ` [PATCH v2] " Junio C Hamano
2026-10-19 23:47 ` Todd Zullinger
2026-10-20 0:30 ` brian m. carlson
2026-10-20 0:54 ` Todd Zullinger
2026-10-20 1:14 ` Junio C Hamano
2026-10-20 5:50 ` Patrick Steinhardt
2026-10-20 14:16 ` Junio C Hamano
2026-10-20 4:25 ` [PATCH v3] " Junio C Hamano
2026-10-20 15:58 ` [PATCH v4] github-ci: update macos jobs from macos-14 Junio C Hamano
2026-10-20 17:15 ` Junio C Hamano
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=atXC91tL7MHRioPZ@pks.im \
--to=ps@pks.im \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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