setup-python: Post setup Python step fails (pipenv cache)

      - uses: actions/setup-python@v4
        with:
          python-version: "3.8"
          cache: pip

The error occurs when the job specifies the use of cache but in fact is not using it. Should this affect the entire job? Can the error be converted to a warning so a job is not considered failed?

Same for me.

      - uses: actions/setup-python@v4
        with:
          python-version: 3.11
          cache: 'pipenv'

Error: Cache folder path is retrieved for pipenv but doesn't exist on disk: /home/runner/.local/share/virtualenvs

I’m seeing this error too.

At the risk of sounding very obvious, but maybe this’ll help someone in any case:

We ran into this issue recently. (For example; see here.)

What ‘fixed’ it for us was the realization that whenever this issue occurred, the workflow as a whole needed to skip all the steps that actually required python and/or pip – and then to disable the setup-python step as well whenever that was the case.

(That might also be going on with the reproduction of others’ but in a more subtle way: All of the actions taken that I can see here are for packages that are likely to be included and at latest version anyway, so the cache might never get written to. Again, sorry if that was already obvious.)

In any case, however inelegant it may be, setting up something, not using it, and then cleaning it up again should probably (also) not result in an error. (Just putting that out there, since that is a slightly different case than what OP is talking about, which may or may not require a different approach to solve.)

Hi @dmitry-shibanov no updates beyond that this is still an issue. I tried removing the cache key which obviously removes the error but after adding it back, the error came back too. So I am stuck it seems between not having caching or receiving this error. I don’t have this confirmed yet, but I suspect this error happens only on the master branch and not in other branches. Also this is interesting to me, after I added back the cache key, the next run produced this:

Run actions/setup-python@v3.1.2
  with:
    cache: pipenv
    python-version: 3.9.13
    token: ***
Successfully setup CPython (3.9.13)
pipenv cache is not found

And then in post step

Post job cleanup.
Error: Cache folder path is retrieved for pipenv but doesn't exist on disk: /home/runner/.local/share/virtualenvs