-
Notifications
You must be signed in to change notification settings - Fork 54
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
Sccache is not working after resume on macOS-12 #174
Comments
… version (llvm#77165)" This reverts commit 602c8fa, due to an sccache issue seen on larger builds using macOS-12 runners. The issue is documented in in the following issue: hendrikmuhs/ccache-action#174 The original PR is the following: llvm#77165
Am I getting this right:
So the issue seems to be with the sccache binary on the newer macos? This doesn't seem to be an issue with the action, however it is good to keep this issue as a warning for others. |
… version (#77165)" (#77270) This reverts commit 602c8fa, due to an sccache issue seen on larger builds using macOS-12 runners. The issue is documented in in the following issue: hendrikmuhs/ccache-action#174 The original PR is the following: #77165
@hendrikmuhs, yes, I bumped the runner version from
Very possible.
It looks like brew is installing the same version, 0.7.4, on macOS-11 as it does on macOS-12, but it takes massively more time to install on macOS-11 (like 20 mins vs 20 seconds). |
I was concerned that the restore and save actions might be somehow invoking different versions of sccache, like the error says:
Or, maybe the save action is being invoked too close to the last compilation, causing corruption? |
… version (llvm#77165)" (llvm#77270) This reverts commit 602c8fa, due to an sccache issue seen on larger builds using macOS-12 runners. The issue is documented in in the following issue: hendrikmuhs/ccache-action#174 The original PR is the following: llvm#77165
On macOS-12, sccache is not working after cache resuming and then fails to post stats during the cleanup.
The latter issue causes the new cache to not be saved.
Checkout the following consecutive builds:
Build Job 48
This started with no prior cache and ran for 2h 7m 38s.
In between Jobs Canceled Without Starting
Build Job 50
This build started with Job 48's cache and ran for 2h 4m 11s.
In between Jobs Canceled Without Starting
Build Job 53
This build started with Job 48's cache, also, and ran for 2h 5m 4s.
These and more recent builds can be seen here.
The text was updated successfully, but these errors were encountered: