-
Notifications
You must be signed in to change notification settings - Fork 551
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
Multi-job workflow with cache & poetry fails #424
Comments
Hello @Vichoko. Thank you for your report. Could you please try to add this command: |
Thanks for your quick response! I was just trying that (but with py 3.8), and it continue failing but with a different error:
It seems to be trying to use python 3.6, but I'm not sure why. |
I believe I’ve run into the same issue |
Hi, @Vichoko 👋 ! Here you encountered a well-known Poetry's issue . Poetry tends to use the system's version of the python that is why in the first job (on Ubuntu 20.04) it uses: 3.8.12 and in the second (Ubuntu 18.04): 3.6.9 Actually, we have one open issue related to this topic with workarounds available in the comments. By now I'm going to close this issue, If you have any questions - feel free to ping us! |
Description:
I started migrating from
actions/cache@v2
tosetup-python
's cache.I followed the workflow schema for poetry shown in the README.md to create a workflow with 3 jobs:
When running a workflow with more than 1 job that uses poetry with cache enabled, only the first job finishes successfully but subsequent jobs fails with the following error:
Action version:
actions/setup-python@v4
Platform:
Runner type:
Tools version:
Repro steps:
This is happening in my linter workflow:
Expected behavior:
The second job should run smoothly.
Actual behavior:
The second job is failing on
poetry install
step with the error stated in the description of this issue. It seems to be trying to install the dependencies, even though they should be cached from the first job. So apparently, the cache isn't working. Should it skip the poetry install step if the cache was restored?The text was updated successfully, but these errors were encountered: