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
Any idea why ccache not working for this publish-docker
workflow (but it does for this other unixlike-builds CI
workflow)?
#108
Comments
What exactly does it mean to "not work" in this case? The second seems to save the cache so that looks like it's "working". |
If you see the step |
I think this "issue" may be related, if not the same, to this other: docker/build-push-action#433 They say there that pushing to a new tag doesn't use the existing cache. |
Can you please link to two subsequent GHA runs that show this behaviour? So far we‘ve only seen a single one that populates the cache. |
The commits were made on two different branches. They do not share caches by GHA design. Did you expect a cache from master/main to be used in one of the builds? |
All the work I'm doing lately is on the |
Hm you're right, something is not working here. Is your repository reaching the cache size limit? |
I don't believe so. Cache is being saved successfully. It's taking 51MB out of a 500MB max size. Have a look at the first link again:
|
I was wondering about repository level cache limit, but honestly that's just a last straw, I really have no ideas left :( |
@jonashaag many thanks for you attention anyway! |
Hi!
I believe I'm following exactly the same steps in these two workflows:
https://github.com/rturrado/the_modern_cpp_challenge/tree/unixlike-builds/.github/workflows
ubuntu-22.04
runner.gcc
12.ccache
with a key named after the job name.However,
ccache
works in one of the workflows:https://github.com/rturrado/the_modern_cpp_challenge/actions/runs/3264947175/jobs/5366385462
(see step
ccache
/Restore cache
).But not in the other:
https://github.com/rturrado/the_modern_cpp_challenge/actions/runs/3264957407/jobs/5366408088
Thanks!
The text was updated successfully, but these errors were encountered: