Post setup Python step fails (pipenv cache)
See original GitHub issueDescription: A clear and concise description of what the bug is.
Hey! So this used to work just a few days ago. We’ve been having some issues with cache in the last few days (see here for details), this is a brand new issue which I think might or might not be related to the previous problem. Simply put, the action fails in the post step with the following message.
Post job cleanup.
[2](https://github.com/<org>/<repo>/runs/6889538635?check_suite_focus=true#step:20:2)
Error: Cache folder path is retrieved for pipenv but doesn't exist on disk: /home/runner/.local/share/virtualenvs
Here’s the actual step:
Run actions/setup-python@v3.1.2
[2](https://github.com/<org>/<repo>/runs/6889538635?check_suite_focus=true#step:5:2)
with:
[3](https://github.com/<org>/<repo>/runs/6889538635?check_suite_focus=true#step:5:3)
cache: pipenv
[4](https://github.com/<org>/<repo>/runs/6889538635?check_suite_focus=true#step:5:4)
python-version: 3.9.13
[5](https://github.com/<org>/<repo>/runs/6889538635?check_suite_focus=true#step:5:5)
token: ***
[6](https://github.com/<org>/<repo>/runs/6889538635?check_suite_focus=true#step:5:7)
Successfully setup CPython (3.9.13)
[7](https://github.com/<org>/<repo>/runs/6889538635?check_suite_focus=true#step:5:8)
pipenv cache is not found
Action version: Specify the action version
3.1.2
Platform:
- Ubuntu
- macOS
- Windows
Runner type:
- Hosted
- Self-hosted
Tools version:
3.9.13
Repro steps:
A description with steps to reproduce the issue. If your have a public example or repo to share, please provide the link.
Expected behavior: A description of what you expected to happen.
No issue occurs, the same way it used to work a week ago.
Actual behavior: A description of what is actually happening.
This error message appears on every run.
Issue Analytics
- State:
- Created a year ago
- Reactions:4
- Comments:12 (2 by maintainers)
Top GitHub Comments
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 themaster
branch and not in other branches. Also this is interesting to me, after I added back thecache
key, the next run produced this:And then in post step
It would appear the pipenv cache implementation assumes it will be at this location, making
PIPENV_VENV_IN_PROJECT
probably unworkable at present versions of setup-python actions: https://github.com/actions/setup-python/blob/main/src/cache-distributions/pipenv-cache.ts#L25