curved-television-6568
03/15/2023, 5:18 PMinit-pants
GH action, and get slightly confused wrgt remote caching..`cache-lmdb-store`: Pass the stringThis suggests that remote caching does work, while:to enable caching pants’ lmdb store in a GHA cache. By default, this action does NOT cache the'true'
. This is a very coarse cache that can grow unbounded. So, it is very likely to hit GitHub’s 10GB per repo max for action caches. If you enable this, you need another process or workflow to manage discarding older GHA caches, or minimizing the cache size as described in the docs. Use the default if using remote caching.lmdb_store
This action does not use any secrets at this point. It might need some once it supports projects that use remote caching.Seems to say it doesn’t.. 🤷
proud-dentist-22844
03/15/2023, 5:41 PMcurved-television-6568
03/15/2023, 5:51 PMproud-dentist-22844
03/15/2023, 5:52 PMfast-nail-55400
03/15/2023, 5:52 PMcurved-television-6568
03/15/2023, 5:54 PMinit-pants
for that.. we’ll see how far I get with this 🙂proud-dentist-22844
03/15/2023, 5:54 PMcurved-television-6568
03/15/2023, 5:55 PMinit-pants
action. I do however get this on the “Post action” phase of the run:
Warning: Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved.
I think it is for the “Cache Pants named caches” step. This is running in a container, so user/home etc tend to be wonky (e.g. root)."*named*_caches_dir": ".cache/pants/named_caches"
wouldn’t have expected a relative path here…pants.ci.toml
file.. 😜init-pants
action assumes default paths rather than looking at the configuration..