-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
github actions now fail for python2 and ubuntu clang and ubuntu swift #3988
Comments
Sure, will investigate later tonight. |
The workflow is setup to work on Ubuntu-20.04 and the default 'latest' is migrating to Ubuntu-22.04 which isn't supported yet (all the dependent actions needs to support the platform before the workflow can use it). Switching all platforms to use explicit versions rather than the '-latest' tag so the transition is more voluntary than something that just happens behing the scene.
The workflow is setup to work on Ubuntu-20.04 and the default 'latest' is migrating to Ubuntu-22.04 which isn't supported yet (all the dependent actions needs to support the platform before the workflow can use it). Switching all platforms to use explicit versions rather than the '-latest' tag so the transition is more voluntary than something that just happens behing the scene. Also, upgraded all setup-xx actions to latest versions to remove some of the deprecation warnings on dashboard. Setup concurrency as well (kill any existing build running on the same branch branch and using the same workflow).
The workflow is setup to work on Ubuntu-20.04 and the default 'latest' is migrating to Ubuntu-22.04 which isn't supported yet (all the dependent actions needs to support the platform before the workflow can use it). Switching all platforms to use explicit versions rather than the '-latest' tag so the transition is more voluntary than something that just happens behing the scene. Also, upgraded all setup-xx actions to latest versions to remove some of the deprecation warnings on dashboard. Setup concurrency as well (kill any existing build running on the same branch branch and using the same workflow).
The workflow is setup to work on Ubuntu-20.04 and the default 'latest' is migrating to Ubuntu-22.04 which isn't supported yet (all the dependent actions needs to support the platform before the workflow can use it). Switching all platforms to use explicit versions rather than the '-latest' tag so the transition is more voluntary than something that just happens behind the scene. Also, upgraded all setup-xx actions to latest versions to remove some of the deprecation warnings on dashboard. Setup concurrency as well (kill any existing build running on the same branch branch and using the same workflow). Signed-off-by: HS <[email protected]>
I am unsure what you are trying to do with #3984 (issue lacks detail) but I have fixed the CI build issues with the current dev #3989. The problem was with the use of 'XXX-latest' machines. The definition of 'latest' changes behind the scene when the GitHub team decides it's time to upgrade. Unfortunately, all the actions used in the workflow don't recognize that new platform simultaneously and builds starts failing. I have updated the workflow so that the upgrade is now manual, and thus controlled. You will see warnings in the workflow run when a new version is available and you can choose when it's good time to upgrade (of course before the end-of-life of the current used version). |
Fixed by #3989 |
Hi @hs-apotell any chance you could take a quick look to see about getting python2 / clang / swift up and running again?
https://github.com/antlr/antlr4/actions/runs/3551377074/jobs/5965500626
We're working on getting swift to reuse the same runtime lib but it works locally (just really slowly): #3984
Here are the errors related to install for actions:
The text was updated successfully, but these errors were encountered: