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
{{ message }}
Repository navigation
Test Python Package Installation tests are flaky #1122
On a deeper look, this is not a flaky test, it is just failing. Python2 + poetry is not a combination that can be easily supported. Best suggestion is to remove that combination and state that we can't run on it.
I looked over actions/setup-python#374 a bit, and I don't think that's the cause of it, since we're not using the setup-python action in those tests at all.
Instead I think we're running into a similar problem, the poetry installation (under Python 3) on windows is not able to find the Python 2 executable.
Found poetry.lock, will install packages with poetry
+ C:\hostedtoolcache\windows\Python\3.10.5\x64\python.exe -m poetry install --no-root
...
The currently activated Python version 3.10.5 is not supported by the project (^2.7).
Trying to find and use a compatible version.
NoCompatiblePythonVersionFound
Poetry was unable to find a compatible version. If you have one, you can explicitly use it via the "env use" command.
Activity
aeisenberg commentedon Jun 24, 2022
On a deeper look, this is not a flaky test, it is just failing. Python2 + poetry is not a combination that can be easily supported. Best suggestion is to remove that combination and state that we can't run on it.
More information: actions/setup-python#374
RasmusWL commentedon Jun 28, 2022
I looked over actions/setup-python#374 a bit, and I don't think that's the cause of it, since we're not using the
setup-pythonaction in those tests at all.Instead I think we're running into a similar problem, the poetry installation (under Python 3) on windows is not able to find the Python 2 executable.
From the logs of a failure.
aeisenberg commentedon Jun 28, 2022
Right, I don't think it is caused by actions/setup-python#374, but it is the same underlying issue. Thanks for taking a deeper look here.