Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ci: Switch to macOS 14 on M series chips #377

Merged
merged 1 commit into from
Apr 11, 2024

Conversation

neverpanic
Copy link
Collaborator

@neverpanic neverpanic commented Apr 11, 2024

Description

macOS 12 was released in October 21, and since then 13 has been out in October 22, and 14 in September 23. Switch to a more recent Mac operating system since that's likely what users will be running.

See [1] for GitHub's list of available shared runners. From the macos-12 label to the macos-14 label, the number of CPU cores stays the same (3), but the CPU architecture switches from x86_64 to arm64. All other parameters stay the same except for RAM, which changes from 14 GB to 7 GB. Since pkcs11-provider is not a memory intensive project, this likely has negligible impact on us. The new CPU architecture can be helpful to identify hardware-specific issues, so is probably a net positive. The M series chips are also typically much faster than the older Intel counterparts.

Checklist

  • Code modified for feature
  • Test suite updated with functionality tests
  • Test suite updated with negative tests
  • Documentation updated

Reviewer's checklist:

  • Any issues marked for closing are addressed
  • There is a test suite reasonably covering new functionality or modifications
  • This feature/change has adequate documentation added
  • Code conform to coding style that today cannot yet be enforced via the check style test
  • Commits have short titles and sensible commit messages
  • Coverity Scan has run if needed (code PR) and no new defects were found

macOS 12 was released in October 21, and since then 13 has been out in
October 22, and 14 in September 23. Switch to a more recent Mac
operating system since that's likely what users will be running.

See [1] for GitHub's list of available shared runners. From the macos-12
label to the macos-14 label, the number of CPU cores stays the same (3),
but the CPU architecture switches from x86_64 to arm64. All other
parameters stay the same except for RAM, which changes from 14 GB to
7 GB. Since pkcs11-provider is not a memory intensive project, this
likely has negligible impact on us. The new CPU architecture can be
helpful to identify hardware-specific issues, so is probably a net
positive. The M series chips are also typically much faster than the
older Intel counterparts.

[1]: https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners/about-github-hosted-runners#standard-github-hosted-runners-for-public-repositories

Signed-off-by: Clemens Lang <[email protected]>
@neverpanic
Copy link
Collaborator Author

This is also nice because the macOS-14 run is now actually the first CI step to finish :)

@neverpanic neverpanic requested review from Jakuje and simo5 April 11, 2024 14:30
Copy link
Contributor

@Jakuje Jakuje left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm.

Does it make sense to run also on the older one for some compatibility?

@neverpanic
Copy link
Collaborator Author

Does it make sense to run also on the older one for some compatibility?

IIRC Simo only wanted one.

I also think we don't really need to continue supporting older macOS releases for a longer time, plus there's really nothing in pkcs11-provider that would behave in a different way on an older macOS. I don't think there's a lot of added value by testing older macOS.

@simo5 simo5 merged commit f3d6bab into latchset:main Apr 11, 2024
27 checks passed
@neverpanic neverpanic deleted the ci-macos-14 branch April 11, 2024 14:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants