-
Notifications
You must be signed in to change notification settings - Fork 35
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
Use mozilla-actions/sccache-action for caching builds #411
Conversation
4f09441
to
ca4f63a
Compare
I ran the GitHub Action initially here, and then pushed a commit with an amended timestamp to get a new SHA so that it would run again using the cache it had created. That re-ran here, but hit what looks like a test flake on The first initial run reported a total duration of 17m 54s, and the third run took 13m 58s. The "Post Run sccache-cache" step prints out stats about reuse. For example:
|
Co-authored-by: Kevin P. Fleming <[email protected]>
Co-authored-by: Kevin P. Fleming <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There seems to be something weird with with how we're using the GitHub Action cache that both @kpfleming and I have hit today that's breaking the test CI. I've had a good experience using mozilla-actions/sccache-action elsewhere, so I've made this PR to try out using it instead of saving and restoring the
target/
directories. I've adjustedactions/cache
to only save~/.cargo/registry
.