macOS 15 runner getting stuck

[NachoSoto]

Description

I have 3 different jobs using 20250120.596 that are stuck after 2 hours, when they normally take ~10minutes.

Platforms affected

• Azure DevOps
• GitHub Actions - Standard Runners
• GitHub Actions - Larger Runners

Runner images affected

• Ubuntu 20.04
• Ubuntu 22.04
• Ubuntu 24.04
• macOS 13
• macOS 13 Arm64
• macOS 14
• macOS 14 Arm64
• macOS 15
• macOS 15 Arm64
• Windows Server 2019
• Windows Server 2022
• Windows Server 2025

Image version and build link

20250120.596

Is it regression?

Yes, 20250124.610 does not have this issue

Expected behavior

Jobs don't get stuck

Actual behavior

Job has been running for over 2 hours when it takes ~11 minutes.

Repro steps

Use 20250120.596

[sangeeths03]

Hi @NachoSoto , I will check on the issue and keep you updated on the progress.

[sangeeths03]

Hi @NachoSoto ,

We’ve encountered some performance issues with macOS 15 and macOS 15 ARM, which prompted us to roll back to previous versions for now. Given these performance concerns, we are currently conducting some additional performance tests.

Once we have validated the results, we will deploy the latest macOS 15 ARM version. We’re closely monitoring this, and as soon as the VM rollout is complete, the issue should be resolved, I believe.

We appreciate your patience, and we’ll keep you updated on our progress. Thanks!

I tested my workflow with the 20250120.596 version, and it hasn’t been taking extra time for me. Could you please share the sample workaround steps or a sample workflow where you’re encountering this issue? I’ve attached a screenshot showing the 20250120.596 version, and I’m not experiencing any issues as you mentioned.

[sangeeths03]

@NachoSoto ,We have deployed the latest macOS 15 and macOS 15 ARM versions and are currently monitoring for any performance issues. Once the performance checks are complete, we will provide an update. After that, you can proceed with running the jobs, and we believe this should resolve the issue.

[sangeeths03]

Hi @NachoSoto, could you please confirm if the issue is resolved now that the new macOS 15 ARM image versions have been deployed? We’re hoping this has addressed the problem—let us know if we can proceed with closing the issue.