Skip to content

Use macos-26 runners and test on Intel/ARM#2348

Draft
sirosen wants to merge 2 commits intojazzband:mainfrom
sirosen:use-explicit-macos-runners
Draft

Use macos-26 runners and test on Intel/ARM#2348
sirosen wants to merge 2 commits intojazzband:mainfrom
sirosen:use-explicit-macos-runners

Conversation

@sirosen
Copy link
Member

@sirosen sirosen commented Mar 6, 2026

Open as a draft because I think this needs to be linked to relevant issues. It also needs to actually run in CI to confirm it works as desired.

  • In CI, separate OS name from runner version
  • Update CI to test both Intel and ARM macOS
Contributor checklist
  • Included tests for the changes.
  • A change note is created in changelog.d/ (see changelog.d/README.md
    for instructions) or the PR text says "no changelog needed".
Maintainer checklist
  • If no changelog is needed, apply the bot:chronographer:skip label.
  • Assign the PR to an existing or new milestone for the target version
    (following Semantic Versioning).

sirosen added 2 commits March 5, 2026 23:02
In the matrix config, separate the notions of "os.name" (the nice name
shown in the CI GUI) from "os.runs_on" (the value used for selecting the
runner).

They are still aligned after this change, but can now be manipulated
independently.
Pin the macOS CI runners specifically to `macos-26` and `macos-26-intel`.
@sirosen
Copy link
Member Author

sirosen commented Mar 6, 2026

This appears to be working as desired, but I find the results in CI wall clock time a bit concerning.
CI time in this PR seems to be dominated by macOS runs, and they're taking ~10 minutes (or 100%) more time to complete than previous CI runs, e.g. on main.

I'm also worried that by increasing the number of builds by so much, we're increasing the changes of flaky failures. We want to solve those anyway, but "want to fix" != "have fixed".

Many projects consider it sufficient to test their max and min Python versions on Windows and macOS. I think I would be comfortable doing that at least for these new Intel-mac builds, to keep CI times more under control. It would require refactoring the job config a bit, but I think it's necessary.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant