Description:
I'm using setup-python@v5 on a MacOS self hosted runner and when configuring a Python interpreter not previously cached already I'm getting this:
So it's trying to use sudo and interactively asking me for a password to create the new version. I have the cache directory configured properly with write permissions as described in the documentation:
dnwillia@snps-wcvmpdkkvosy Python % pwd
/Users/runner/hostedtoolcache/Python
dnwillia@snps-wcvmpdkkvosy Python % ls -al
total 0
drwxr-xr-x 4 dnwillia staff 128 Apr 23 14:49 ./
drwxr-xr-x 3 dnwillia staff 96 Apr 23 13:27 ../
drwxr-xr-x 4 dnwillia staff 128 Apr 23 14:42 3.10.11/
drwxr-xr-x 4 dnwillia staff 128 Apr 23 14:49 3.13.13/
I managed to get 3.13 installing by interactively starting the runner and typing in the password manually when the action was executed. This allowed things to proceed correctly after the 3.13.13 area was created.
Looking at the issues this kind of smells like #1301 too. The symlinks are created in my case though once I type a password.
Action version:
v5
Platform:
Runner type:
Tools version:
See above, Python 3.13.
Repro steps:
Just create a basic action using setup-python@v5 to install a Python interpreter.
Expected behavior:
The interpreter installs correctly.
Actual behavior:
The interpreter does not get installed and the workflow stops execution.
Description:
I'm using setup-python@v5 on a MacOS self hosted runner and when configuring a Python interpreter not previously cached already I'm getting this:
So it's trying to use sudo and interactively asking me for a password to create the new version. I have the cache directory configured properly with write permissions as described in the documentation:
I managed to get 3.13 installing by interactively starting the runner and typing in the password manually when the action was executed. This allowed things to proceed correctly after the 3.13.13 area was created.
Looking at the issues this kind of smells like #1301 too. The symlinks are created in my case though once I type a password.
Action version:
v5
Platform:
Runner type:
Tools version:
See above, Python 3.13.
Repro steps:
Just create a basic action using setup-python@v5 to install a Python interpreter.
Expected behavior:
The interpreter installs correctly.
Actual behavior:
The interpreter does not get installed and the workflow stops execution.