-
Notifications
You must be signed in to change notification settings - Fork 12
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
CI: Caching #41
Comments
In particular, look at how conjure itself does it - it does That way, you never need to delete then resave the cache as I do, you just make one with a newer timestamp and let github GC them all. |
Caching isn't quite satisfactory at the moment, not entirely sure why. PR #99 just failed to find a cache even though I just made small incremental changes. See https://github.com/conjure-cp/conjure-oxide/actions/runs/6950773148/job/18911526725?pr=99
I suggest (unless people see a reason not to do this)
|
I came across this before and was suspecting an emdash or something in the GitHub cache match somewhere - there's no reason why it shouldn't match as it currently is. Changing it entirely will be easier than debugging this I imagine |
@ozgurakgun seems to be fixed? |
Continue work done on #36, #37.
In short: we want to create a sensible caching scheme that allows all crates in this project to be cached, and updated as appropriate so that PRs do not need to clean build things. Some actions only use one crate, some use two, some use them all, so the caching needs to be invariant to this.
There were a few problems and approaches to these discussed in #36 #37.
The text was updated successfully, but these errors were encountered: