Duplicate caching in R-CMD-check and test-coverage actions
#591
Comments
milanmlft
added a commit
to LearnToDiscover/sandpaper
that referenced
this issue
Jun 4, 2024
`r-lib/actions/setup-r-dependencies` already takes care of caching See also carpentries#591
milanmlft
added a commit
to LearnToDiscover/sandpaper
that referenced
this issue
Jun 6, 2024
* Avoid duplicate caching `r-lib/actions/setup-r-dependencies` already takes care of caching See also carpentries#591 * Further simplify the `R-CMD-check` action * Upgrade `actions/checkout` to `v4`
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi sandpaper devs!
I noticed while working on a fork of
sandpaperthat the CI is producing quite a lot of caches on the GitHub Action runners. Upon further inspection, I think this is due because there are 2 caching steps happening in theR-CMD-checkandtest-coverageactions:"Restore {renv} cache"step"Setup dependencies"step which callssetup-r-dependenciesfromr-libThe problem is that
setup-r-dependenciesdoes its own caching by default.I think they're meant to cache pretty much the same thing (R dependencies of
sandpaper), though I'm not sure why therenvcaches are typically bigger. In any case I think you only need one of them and having both can eat up quite a lot of caching storage space (might want to check this for the Carpentries organisation).I'd suggest removing the
Restore {renv} cachestep (and the dependentPrime {renv} Cache) and letsetup-r-dependencies handle the caching. That would also reduce the amount of code to maintain for thesandpaper` devs 😉Happy to create a PR for this!
The text was updated successfully, but these errors were encountered: