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
Reacted by Chris Sargent, Dobrosław Żybort, Matthieu MOREL, Pierre R, Stijn De Haes, Gareth Jones, Paweł Mitka, Futa HIRAKOBA, Miyata Jumpei, Matt Braymer-Hayes and 17 more
Reacted by Sebastian Stammler, Dirk Nilius and hcscctv
Hello everyone. We released the new version of setup-go with caching support and updated major tag. For now I'm going to close the issue if you have any concerns feel free to ping us.
with the built-in cache, but seems like it's not achieving the same result, as the build time is up to 3-4 minutes form ~40s-1m.
I suspect this is because it needs to download the modules instead of using the cached ones, any ideas?
EDIT: It might be because I have the setup in different jobs, but the key is always the same, so the cache is not updated? I used to have different keys, for like the unit tests and the build
Activity
sebastianst commentedon Feb 17, 2022
That'd be awesome. For reference,
actions/cacherecommends the following step in your job for Go repos (Linux):A nice start would be to mention this
actions/cachesetup in the README.nc-dirknilius commentedon Mar 25, 2022
It's a bit sad as this is the only
setupaction we use without build-in cache support.setup-nodealready mentioned, in addition seehttps://github.com/marketplace/actions/setup-java-jdk#caching-packages-dependencies https://github.com/marketplace/actions/setup-ruby-jruby-and-truffleruby#caching-bundle-install-automatically
https://github.com/marketplace/actions/setup-python#caching-packages-dependencies
dmitry-shibanov commentedon May 30, 2022
Hello everyone. We released the new version of setup-go with caching support and updated major tag. For now I'm going to close the issue if you have any concerns feel free to ping us.
lucacome commentedon Aug 6, 2022
Hello, I replaced
with the built-in cache, but seems like it's not achieving the same result, as the build time is up to 3-4 minutes form ~40s-1m.
I suspect this is because it needs to download the modules instead of using the cached ones, any ideas?
EDIT: It might be because I have the setup in different jobs, but the
keyis always the same, so the cache is not updated? I used to have different keys, for like the unit tests and the builde-korolevskii commentedon Aug 10, 2022
Hello @lucacome
Could you please open a separate issue with a detailed description and steps to reproduce it?
same-id commentedon Mar 23, 2023
Maybe perhaps this is because there are not "restore-keys", only exact match on primary key?
At least this is what I'm trying to understand now