Error: Cache folder path is retrieved for poetry but doesn't exist on disk

[yuliswe]

Description:
My CI is failing with this error in the Post job cleanup step, I don't know what it means:

Post job cleanup.
Error: Cache folder path is retrieved for poetry but doesn't exist on disk: /home/runner/.cache/pypoetry/virtualenvs, /home/runner/work/FastchargeAPI/FastchargeAPI/.venv

My workflow file is simply:

- uses: actions/setup-python@v3
  with:
    python-version: "3.9"
    cache: "poetry"

Action version:
'actions/setup-python@v3' (SHA:48e4ac706204bab735867521ba54b3276c883d00)

Platform:

• Ubuntu
• macOS
• Windows

Runner type:

• Hosted
• Self-hosted

Tools version:
Python3.9, Python3.10

[yuliswe]

Can someone explain to me why it is trying to look for a cache folder in these locations and why are they missing? This is not coming from my code. I think it's something internal to setup-python. If I remove cache: "poetry" the problem disappears.

[dmitry-shibanov]

Hello @ylilarry. Thank you for your report. Could you please attach a link to public repository to reproduce the issue ? Could you please try to use actions/setup-python@v4 ?

[dmitry-shibanov]

Hello @ylilarry, just a gentle ping.

[yuliswe]

Hi, let me check it tonight. Thanks for the reminder.

[MaksimZhukov]

Hello @ylilarry !
Have you had a chance to prepare a public repository for further investigation?

[yuliswe]

The problem is sporadic and I can't reproduce it. Will take a look if this happens again.

[sezanzeb]

I'm having a similar error message with cache: 'pip': https://github.com/sezanzeb/input-remapper/actions/runs/5365366969/jobs/9734150591#step:9:2

Should I open a separate issue for that? Is something on our side broken?

[dmitry-shibanov]

Hello @sezanzeb. Could you please open a separate issue ?

[devanubis]

When I came across this problem, it turned out to be because my project was using a local .venv in development (to give the `pyright` pre-commit hook easy access to our dependencies and types)

And in our ci workflow, poetry was then installing to that .venv too, but setup-python was still looking for the poetry virtual environment in /home/runner/.cache/pypoetry/virtualenvs.

I just added a step to our ci workflow to rm -rf .venv since we don't need/want a local venv in ci.

Might help anyone else running into this.