-
-
Couldn't load subscription status.
- Fork 1.8k
tests: try to fix ubuntu bionic tests #13424
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
Conversation
by forcing an older nodejs
|
Bionic has been EOL since 2023-05-31. I'd say let's move that container to Focal instead. |
|
Bionic currently tests that we maintain support for Python 3.7 (and I don't want to bump the minimum version of python until we are using features that require the new version -- we still occasionally get complaints that meson dropped 3.6 support but I spearheaded that upgrade because of tangible developer advantages in moving to 3.7, not just "GitHub broke the CI so we don't test it"). Beyond that, I saw at least one claim that the GitHub Actions nodejs issue affects Ubuntu 20.04 (focal) containers as well, but I haven't verified. |
|
Fine with me either way. This makes the CI green though in the meantime. |
|
A middle ground could be Debian Buster, Python 3.7, newer glibc, EOL since two weeks. |
|
In the interest of having a green CI, I'm going to merge this. If we want to move to Focal or Buster we can do that as a separate PR |
|
thanks! |
Keep using v3 for Bionic because of mesonbuild#13424
Keep using v3 for Bionic because of #13424
Keep using v3 for Bionic because of mesonbuild#13424
Keep using v3 for Bionic because of mesonbuild#13424
by forcing an older nodejs
the node v20 build no longer works in bionic. While actions/checkout@v3 uses node v16 GHA forced it to use v20 some time ago after a deprecation cycle. This env var makes it use v16 again, despite that being EOL.