Unable to execute actions/setup-python #251
Comments
|
I've hit the same issue, I've found that if you set a |
|
I'm not sure, but I think it fails because I'm running it on osx, but the installation is running through the docker container on linux, and it's not understanding which version it should install. I think? :) The manifest does contain the right version it should use: https://raw.githubusercontent.com/actions/python-versions/master/versions-manifest.json |
|
For the records I'm running it under Ubuntu 19.10 |
|
So good. |
|
Same here, and I'm using ElementaryOS under Ubuntu 18.04.4. Some of you guys tried with another image? Just wondering if this may solve, cause I couldn't try with the alternative image, my disk space it's insufficient :( |
|
@RaulBSantos it does work running Since that's fine enought for me I'll add the -P option to my .actrc. For other user willing to push the investigation, the setup-python author suggested following this guideline https://github.com/actions/setup-python#using-setup-python-with-a-self-hosted-runner. I gave it a quick shot without success. |
|
Yep, I'm having the exact same problem here as well. On macOS, always gives me the the Setting the |
|
I created a simple test file which re-creates the problem name: pull_requests
on: [pull_request]
jobs:
test_pr:
runs-on: ubuntu-18.04
steps:
- name: Set up Python
uses: actions/setup-python@v2
with:
python-version: "3.7"It is fixed by adding the Here are the respective lines from the setup-python action: Here is my lsb-release file: EDIT: Removed my previous invalid comment |
|
the problem still exists |
|
In order for this to work, one would write a docker file using Sounds like @rgarrigue tried something like this without success. Bummer. |
|
Still having this problem as well, running Ubuntu 20.04.1 LTS, with 5.4.0-42-generic as my kernel (if that helps or matters at all). |
|
Still a frelling issue |
|
I just ran into this issue as well :( |
|
I solved this by using the method explained by @grische. |
|
Found the problem - - run: |
# Hack to get setup-python to work on act
if [ ! -f "/etc/lsb-release" ] ; then
echo "DISTRIB_RELEASE=18.04" > /etc/lsb-release
fiNot really sure what's the right fix here - It doesn't make sense that @actions/setup-python treats Ubuntu's release version as |
|
Same problem with Ubuntu20.04, @noliran solution solved it |
|
@noliran his solution worked for me. I use it in the following way: # Pull request ci config file
# Note: For local testing with https://github.com/nektos/act use the
# `sudo act -P ubuntu-18.04=nektos/act-environments-ubuntu:18.04` command.
name: MLC pull CI
on:
# Trigger the workflow on a pull request,
# but only for the master branch
pull_request:
branches:
- master
jobs:
build:
name: runner / build
runs-on: ubuntu-18.04
steps:
- uses: actions/checkout@v2
- name: local-fix
run: |
# Hack to get setup-python to work on act
# (see https://github.com/nektos/act/issues/251)
if [ ! -f "/etc/lsb-release" ] ; then
echo "DISTRIB_RELEASE=18.04" > /etc/lsb-release
fi
- name: Set up Python
uses: actions/setup-python@v2
with:
python-version: "3.8" |
|
Related to this pull request actions/toolkit#594. |
|
Issue is stale and will be closed in 14 days unless there is new activity |
|
The PR fixing this issue still hasn't been merged. |
|
This has still been a problem for me on my OSX. I incorporated the "hack" that @noliran mentioned above and deleted the /Users/{myusername}/.cache/act/* and now works as expected.
|
|
Issue is stale and will be closed in 14 days unless there is new activity |
|
Still waiting on actions/toolkit#594 |
|
Hi all, if you will use |
|
It's 2024 and this is still an issue
|
Hi there
Thanks for
act. I've been using it successfully until now, but here's some issue running python related tests : it's unable to execute the setup-python action.I tried with both my "old" act version from a couple of month ago and latest 0.2.8 from GitHub releases. With and without the matrix on python version. With actions/checkout@v1, v2 and master.
And here's the verbose log
The text was updated successfully, but these errors were encountered: