You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
A clear and concise description of what the bug is.
Self-hosted runner fails on Mac Which version of the action are you using?
See this issue with both versions
[ x] v1
[ x] v2
Some other tag (such as v2.0.1 or master)
Environment
self-hosted
Linux
Windows
[x ] Mac
If applicable, please specify if you're using a container
Python Versions
Please list all of the effected versions of Python (3.8.2, etc.)
3.7.3, 3.7.7 To Reproduce
Steps to reproduce the behavior:
If I specify python 3.7.3 or 3.7.7 for the action, it fails
##[error]Version 3.7.3 with arch x64 not found even though that is currently the version on the mac
If I specify python-version: '3.x'
I get the error:
Version 3.x was not found in the local cache
Version 3.x is available for downloading
Download from "https://github.com/actions/python-versions/releases/download/3.8.3-20200514.1/python-3.8.3-macos-1014-x64.tar.gz"
Extract downloaded archive
/usr/bin/tar xz -C ./9c99d59e-64bf-4cba-9166-fe20af925cd6 -f /Users/sanzgiri/actions-runner/_work/_temp/9c99d59e-64bf-4cba-9166-fe20af925cd6
Execute installation script
##[error]The process '/bin/bash' failed with exit code 134
Run/Repo Url
If applicable, and if your repo/run is public, please include a URL so it is easier for us to investigate.
Private Repo
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
I tried out many different settings yesterday and they all fail. I have followed the things suggested in the wiki and what I see in some of the issue comments.
On my Mac, upgraded to the latest OS X 10.15.5:
setup-python v1 fails with
##[error]Version 3.6.7 with arch x64 not found
regardless of the python-version I select in the .yml file for the action.
If I use setup-python@v2, I get a different failure, again regardless of what version of python I use.
Version 3.8.3 was not found in the local cache
Version 3.8.3 is available for downloading
Download from "https://github.com/actions/python-versions/releases/download/3.8.3-20200609.5/python-3.8.3-darwin-x64.tar.gz"
Extract downloaded archive
/usr/bin/tar xz -C ./f839e428-447b-43f7-ae5d-1f2e9e109797 -f /Users/sanzgiri/actions-runner/_work/_temp/f839e428-447b-43f7-ae5d-1f2e9e109797
Execute installation script
##[error]The process '/bin/bash' failed with exit code 134
I looked in the log files under _diag in the runner directory on my mac, but don't see any details on this error (what exit code 134 means here). I have also tried the steps described in the wiki regarding AGENT_TOOLSDIRECTORY and hostedtoolcache
Next, I tried a few different linux configurations (EC2 instances t2.micro, t2.medium, t2.large) running Ubuntu 14.04.
On all of these, I get a different error with setup-python v2
##[error]The process '/bin/bash' failed with exit code 127
Again, I am not able to find additional details on what is causing exit code 127.
My guess is that since the error happens very early (in the installation script) - the actual code in the action is not relevant.
Other things I have tried:
changing repo from private to public.
Appreciate any pointers to resolving this issue or at least getting a better understanding as to what those exit codes mean.
@sanzgiri I followed your tip to downgrade openssl to 1.0.2t but am still getting the error your posted on Jul 26. Did you do anything else?
Create additional symlinks (Required for the UsePythonVersion Azure Pipelines task and the setup-python GitHub Action)
Upgrading PIP...
Error: dyld: Library not loaded: /Users/runner/hostedtoolcache/Python/3.7.7/x64/lib/libpython3.7m.dylib
Referenced from: /Users/bvanlew/actions-runner/_work/_tool/Python/3.7.7/x64/bin/./python
Reason: image not found
Error: ./setup.sh: line 53: 44389 Abort trap: 6 ./python -m ensurepip
Error: The process '/bin/bash' failed with exit code 134`
Activity
sanzgiri commentedon Jun 10, 2020
I tried out many different settings yesterday and they all fail. I have followed the things suggested in the wiki and what I see in some of the issue comments.
On my Mac, upgraded to the latest OS X 10.15.5:
setup-python v1 fails with
regardless of the
python-versionI select in the .yml file for the action.If I use setup-python@v2, I get a different failure, again regardless of what version of python I use.
I looked in the log files under _diag in the runner directory on my mac, but don't see any details on this error (what exit code 134 means here). I have also tried the steps described in the wiki regarding AGENT_TOOLSDIRECTORY and hostedtoolcache
Next, I tried a few different linux configurations (EC2 instances t2.micro, t2.medium, t2.large) running Ubuntu 14.04.
On all of these, I get a different error with setup-python v2
##[error]The process '/bin/bash' failed with exit code 127
Again, I am not able to find additional details on what is causing exit code 127.
My guess is that since the error happens very early (in the installation script) - the actual code in the action is not relevant.
Other things I have tried:
Appreciate any pointers to resolving this issue or at least getting a better understanding as to what those exit codes mean.
sanzgiri commentedon Jul 26, 2020
I tried this again after several weeks. I now see an error is reported:
##[error]dyld: Library not loaded: /Users/runner/hostedtoolcache/Python/3.8.3/x64/lib/libpython3.8.dylib Referenced from: /Users/sanzgiri/actions-runner/_work/_tool/Python/3.8.3/x64/bin/./python Reason: image not found ##[error]./setup.sh: line 53: 9822 Abort trap: 6 ./python -m ensurepip ##[error]The process '/bin/bash' failed with exit code 134 install dependenciesHow can I resolve this?
sanzgiri commentedon Jul 27, 2020
Finally was able to resolve this. Traced it to openssl on the Mac. Had to downgrade it to 1.0.2t.
bldrvnlw commentedon Oct 29, 2020
@sanzgiri I followed your tip to downgrade openssl to 1.0.2t but am still getting the error your posted on Jul 26. Did you do anything else?
bldrvnlw commentedon Oct 29, 2020
I found the solution is documented in the setup-python readme