-
Notifications
You must be signed in to change notification settings - Fork 579
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
setup-python failing due to missing cache directory #328
Comments
I'm seeing it too, also Windows and 3.11 alpha:
I don't think #303 has been released yet, Possibly linked to the release of pip 22 on Sunday? |
Hello @wmmc88! Thank you for the report! |
Hello @wmmc88. Thank you for your report. It's partly related to these changes, but the root cause is different. Previously cache key for pip didn't contain version of the python, that is why cache got hit on the primary key and the action didn't resave it. Now primary and restore keys have been changed and it forces action to resave cache. |
Could this error have a similar cause?
|
Broken with this issue: actions/setup-python#328
Hello @janosh. Yes, It's related to this issue: actions/toolkit#992 |
From what I can tell failures started as windows image updated from 20220123.1 to 20220131.1: actions/runner-images#5009 EDIT: this may be different after all: your error message is not the same and started on previous version -- sorry for spam |
Hello everyone. We released new version with fix (2.3.2). Could you please try to use it and confirm if it works for you? |
@dmitry-shibanov Same here, also still crashing. |
Note that they've not updated the v2 tag (forgot?) so you are probably not testing the new version. My issue was fixed with the Windows workaround, if I modify my workflow to use [email protected] (instead of v2): |
@jku I thought |
That maybe the intended policy but the tag "v2" pointed to release "v2.3.1" until dmitry just updated it Oops, misread, I mean v2 still points to 2.3.1 |
✅ Confirmed fixed with
Thank you! |
Hello everyone. We updated v2 tag. Could you please confirm that everything works as expected ? |
My issues fixed! |
✅ |
It works for us 🚀 Many thanks 🥇 |
Description:
This job on my repo has been failing since #303 was merged in. Only the python 11 alpha variant is failing due to a cache related issue for pip. It fails in the
Post Setup Python
stage.Action version:
master
Platform:
Runner type:
Tools version:
python 3.11.0-alpha
Repro steps:
Run any pipeline with python 3.11.0-alpha on windows.
Expected behavior:
The job should succeed.
The job fails on
Post Setup Python
The text was updated successfully, but these errors were encountered: