Hi, I'm currently setting up Pants in the CI process following this page. However, in the "Nuking" script, it seems that Pants doesn't create

~/.cache/pants/setup

as it shows a warning:

du: cannot access '/home/runner/.cache/pants/setup': No such file or directory

in the GitHub Jobs' logging. I've followed the example from Pants'

python-example

repository like this:

- name: Install pants
     uses: pantsbuild/actions/init-pants@v4-scie-pants
        with:
          gha-cache-key: v0
          named-caches-hash: ${{ hashFiles('path/to/lockfile.lock') }}
          cache-lmdb-store: 'true'

Is anything wrong with what I've set up in the CI process? Thanks before

The CI setup looks fine, but I guess you'll have to tweak that nuking logic to account for the dir not existing at all

@happy-kitchen-89482 Thank you for responding!

I guess you'll have to tweak that nuking logic to account for the dir not existing at all

Yeah, this is a given since it doesn't exist. But I'm wondering if it's possible that I do something wrong that makes that directory doesn't exist, or that Pants use another cache location. I doubt it since I don't set any cache dir anywhere in my repository.

Benjy, does pants still use

.cache/pants/setup

with the scie-pants bootstrapping? I was under the impression that it all ends up in

.cache/nce

? I'd guess the suggested nuking script could at least be tweaked to check

.cache/nce

in addition to the others?

Oh you may be right! Good call.

In my local machine as well, under

.cache/pants

only exists

lmdb_store

and

named_caches

. So, in the CI script, I should nuke

.cache/nce

instead, is that correct?

yeah, that sounds right. I filed https://github.com/pantsbuild/pants/issues/19497 about fixing the docs; thanks for flagging