You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
Description
I have 3 different jobs using
20250120.596
that are stuck after 2 hours, when they normally take ~10minutes.Platforms affected
Runner images affected
Image version and build link
20250120.596
Is it regression?
Yes,
20250124.610
does not have this issueExpected 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
The text was updated successfully, but these errors were encountered: