search

actions / runner-images

GitHub Actions runner images
MIT License
10.27k stars 3.09k forks source link

[macOS] The `macOS 12` Actions runner image will begin deprecation on 10/7/24 and will be fully unsupported by 12/3/24 for GitHub and ADO #10721

Open erik-bershel opened 2 months ago

erik-bershel commented 2 months ago

Breaking changes

GitHub Actions is starting the deprecation process for macOS 12. While the image is being deprecated, You may experience longer queue times during peak usage hours. Deprecation will begin on 10/7/24 and the image will be fully unsupported by 12/3/24

To raise awareness of the upcoming removal, we will temporarily fail jobs using macOS 12. Builds that are scheduled to run during the brownout periods will fail. The brownouts are scheduled for the following dates and times:

Target date

December 3rd, 2024

The motivation for the changes

GitHub Actions maintains the latest two stable versions of any given OS version.

Possible impact

Workflows using the macos-12 image label will be terminated with an error.

Platforms affected

Runner images affected

Mitigation ways

Workflows using the macos-12 image label should be updated to macos-latest, macos-13, macos-14 or macos-15.

erik-bershel commented 2 months ago

Hey @jaimergp! I noticed that last time you bumped the version of macOS. I think https://github.com/conda-forge will be affected now as well.

guyer commented 2 months ago

Somebody jumped the gun? Microsoft-hosted agents > Software already says macos-12 is "deprecated" and the macos-latest image just jumped from macos-12 to macos-14 between October 1st and October 2nd.

AkihiroSuda commented 1 month ago

macos-13 seems still quite flaky:

Any chance to revisit the issue before shutting down the macos-12 instances?

erik-bershel commented 1 month ago

Hey @AkihiroSuda!

Regarding your issue. As I remember it was related to the vz behaviour. Correct me if I wrong, please. If so, there was a workaround here to set cpus: 1 in the examples/experimental/vz.yaml. Had you chance to try it?

AkihiroSuda commented 1 month ago

Hey @AkihiroSuda!

Regarding your issue. As I remember it was related to the vz behaviour. Correct me if I wrong, please. If so, there was a workaround here to set cpus: 1 in the examples/experimental/vz.yaml. Had you chance to try it?

Yes, it mitigated the issue at that time, but the CI became extremely flaky again recently. Switching to macos-15-large seems to be effective to mitigate (not solve) the issue again, apparently

erik-bershel commented 1 month ago

Yes, it mitigated the issue at that time, but the CI became extremely flaky again recently. Switching to macos-15-large seems to be effective to mitigate (not solve) the issue again, apparently

Yeah, initial issue root cause was kinda architectural. Feel free to open another issue if behaviour repeated with macos-15(-large).

QuLogic commented 1 month ago

Until #9966 is fixed, it is not possible for us to update from macos-12 (where it is fixed) to macos-13 runners.

electrocucaracha commented 1 month ago

@erik-bershel macOS-12 runner image offers nested virtualization thru VirtualBox and Vagrant, does these tools will be able on following versions?

erik-bershel commented 1 month ago

Hey @electrocucaracha! Nested virtualisation was a bit painful since macos-13. We need to do some additional testing before stating something - there is a chance for issues to be resolved at the moment. Right now we do not install those tools due the mentioned issues.

ebolyen commented 4 weeks ago

Just wanted to say thanks to the runner team for scheduling these brownouts! Without it, we probably wouldn't have noticed until it was a much larger problem. We've been stuck on macOS-12 for similar reasons to everyone else (hoping that 15 fixes the issue).

srcejon commented 3 weeks ago

Mitigation ways

Workflows using the macos-12 image label should be updated tomacos-13

The bug that prevents building .dmgs on macos-13 is still open: https://github.com/actions/runner-images/issues/7522