the docs on “pants in CI” recommend caching

~/.cache/pants/named_caches

, but in our repo I find that the size of that dir can grow pretty quickly & dramatically. is there a “safe” subset of that dir we could cache to keep our cache sizes small while still reaping some benefits? I feel like when I’ve poked around in that dir before I’ve seen symlinks between different subdirectories, which makes me worry about the feasibility of only caching a subset

see https://github.com/pantsbuild/pants/issues/14364 for more on this topic

🤔 hmmm ok, we do have remote caching set up but don’t see it used as much as we’d like (probably because our code is so tangled it’s very easy to bust the cache). so trying to keep a size-limited local cache around as well to minimize the amount of re-done work in cases like that

the “local cache” is in `~/.cache/pants/lmdb_store`… the named caches only come in to play when you miss the local cache

yes that is the exact use-case we’re trying to solve for

bumping that ticket might be helpful then, yea. John has the most knowledge about the contents of the pex_root