Ubuntu-latest workflows will use Ubuntu-22.04 #6399
Comments
|
The "Runner images affected" tasks list appears to be incorrect as it targets "macOS" instead and not "ubuntu", is that a mischeck? |
|
@Kichura yes, it was a mischeck. thank you! |
|
Does the ubuntu-22.04 install Firefox as a snap package, or directly, or not at all? I'm seeing test failures with that image, and worry that I'll need to either add a Firefox install to my workflow or maybe pin to ubuntu-20.04 for a while. Edit: It appears not to be installed at all: https://github.com/actions/runner-images/blob/main/images/linux/Ubuntu2204-Readme.md#browsers-and-drivers Is that an oversight that will be corrected, or is it deliberate and we all need to adjust? Thanks! |
|
20.04 LTS has actually shipped firefox as a snapd feature in it's desktop variant whereas the server variant does not have it at all - but can be looked into. |
|
We're using ubuntu-latest images for Firefox testing today. I tried ubuntu-22.04 in a PR to see what would happen, and our workflow fails to detect Firefox at all. So it looks like we'll have to either pin to ubuntu-20.04 or install Firefox explicitly to avoid issues. |
|
In one of our repos, Ubuntu 22.04 based tests are failing. I am yet to figure out the issue. But the same tests working with 20.04. |
|
Hello, @aravindavk! |
|
Thanks @erik-bershel |
|
@ddobranic it seems that Ubuntu Mozilla Team still provides official non-snap ESR packages of Firefox via PPA: https://launchpad.net/~mozillateam/+archive/ubuntu/ppa?field.series_filter=jammy Maybe you could coordinate with them, not having any Firefox at all in CI images is quite... limiting. |
|
Is there any updates on Firefox not being included in ubuntu-22.04? |
This fixes an issue that arises due to the crossover of three different problems: 1. Ubuntu 22.04 will be used by default on 'ubuntu' runners on GitHub runners (actions/runner-images#6399). 2. Ubuntu 22.04 ships with `setuptools` version 59.x.x, which has a bug that does not allow an `--editable` installation of packages in `--user` mode. The flag `--user` is presumed regardless, as the location with packages is not writable by normal users (see pypa/pip#7953 and https://bugs.launchpad.net/ubuntu/+source/setuptools/+bug/1994016). 3. We need an `--editable` installation in order to run tests, as the `test_data` folder is loaded with respect to the package root, and not the test root (see for example: https://github.com/xsuite/xpart/blob/45d621ad060bc25d361835bde1ed985609a24c49/tests/test_single_rf_harmonic_matcher.py#L25) Signed-off-by: Szymon Łopaciuk <szymon@lopaciuk.eu>
Pin the GitHub runners to `ubuntu-20.04`. Long term solutions should be explored at some point in the future. This fixes an issue that arises due to the crossover of three different problems: 1. Ubuntu 22.04 will be used by default on 'ubuntu' runners on GitHub runners (actions/runner-images#6399). 2. Ubuntu 22.04 ships with `setuptools` version 59.x.x, which has a bug that does not allow an `--editable` installation of packages in `--user` mode. The flag `--user` is presumed regardless, as the location with packages is not writable by normal users (see pypa/pip#7953 and https://bugs.launchpad.net/ubuntu/+source/setuptools/+bug/1994016). 3. We need an `--editable` installation in order to run tests, as the `test_data` folder is loaded with respect to the package root, and not the test root (see for example: https://github.com/xsuite/xpart/blob/45d621ad060bc25d361835bde1ed985609a24c49/tests/test_single_rf_harmonic_matcher.py#L25) Signed-off-by: Szymon Łopaciuk <szymon@lopaciuk.eu>
|
@Josh-Osmanski yes, we are planning to add Firefox. thank you! |
prepare for 1.0.2 patch release, release cause multiple deps have been upgraded since last release **breaking_change** cause now ubuntu-latest runner is ubuntu 22.04 lts aka jammy see actions/runner-images#6399 so `rustracer-unknown-linux-gnu` requires at least `glibc>=2.35`
Use Ubuntu 20.04 to build binaries. [Protostar v0.8.1](BibliothecaDAO/realms-contracts#270) doesn't have this problem. [Recently, `ubuntu-latest` was updated to use Ubuntu 22.04.](actions/runner-images#6399) > You're better off finding a Python built with a lower glibc requirement which in practice means building on an old version of Linux or an old docker image. pyinstaller/pyinstaller#5669 Probably Fixes #1293
The pointer for `ubuntu-latest` was updated to 22.04 on Oct 3 (see actions/runner-images#6399). We still run tests on 2.7 and 3.6 and should deprecate support separately.
Node.js 12 actions are deprecated. For more information see:
https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/.
Please update the following actions to use Node.js 16:
actions/checkout@v2,
actionsx/prettier@v2,
JohnnyMorganz/stylua-action@1.0.0
ubuntu-latest workflows will use ubuntu-22.04 soon. For more details,
see actions/runner-images#6399
No new release of `actionsx/prettier` action yet, but I updated the
others.
See actions/runner-images#6399 22.04 dropped support for the old python 3.x versions
|
What about gnome? |
Currently, we use ubuntu-latest runners which currently points to ubuntu-20.04, but will point to ubuntu-22.04 soon [1] [1] actions/runner-images#6399 In order to avoid future surprises and proactives check compatibility of our workflows, pin the version to ubuntu-22.04 already. Signed-off-by: Tobias Klauser <tobias@cilium.io>
…hp#2036) ubuntu-latest is currently transitioning to ubuntu-22.04. During this time, you may experience some jobs running on either an ubuntu-20.04 or ubuntu-22.04 runner. You can specify `runs-on: ubuntu-20.04` in your workflow if you need the previous version. https://github.com/actions/runner-images actions/runner-images#6399
ubuntu-latest was updated to Ubuntu 22.04 near the end of 2022, see actions/runner-images#6399
Remove Python 3.6 from the ubuntu-latest target since it's no longer supported actions/runner-images#6399
- `ubuntu-latest` is currently set to Ubuntu-22.04 which we have issues with when linking the bundled OpenSSL library. - `ubuntu-latest` is however in a rollout stage. Therefore, we might either use an instance of Ubuntu-22.04 or Ubuntu-20.04 – see actions/runner-images#6399 - We should set the image to `ubuntu-20.04` until the linking issue with OpenSSL is solved on newer images
…hat changed to ubuntu-22 in dec 2023 actions/runner-images#6399
and others
Breaking changes
Ubuntu 22.04 is ready to be the default version for the "ubuntu-latest" label in GitHub Actions and Azure DevOps.
Target date
This change will be rolled out over a period of several weeks beginning in October, 3. We plan to complete the migration by December, 15th, 2022.
The motivation for the changes
GitHub Actions and Azure DevOps have supported Ubuntu 22.04 in preview mode since May 2022, and starting from August 2022 Ubuntu 22.04 is generally available for all customers. We have monitored customer feedback to improve the Ubuntu 22.04 image stability and now we are ready to set it as the latest.
Possible impact
The Ubuntu 20.04 image has a different set of software than Ubuntu 22.04. The most significant changes are listed in the table below:
2.6.10
2.7.6
3.0.4
3.1.2
Clang-format
Clang-tidy
11.0.0
12.0.0
13.*
14.*
GFortran
10.3.0
-
10.*
11.*
8.0.24
8.1.11
3.1.202
3.1.302
3.1.423
5.0.104
5.0.214
5.0.303
5.0.408
6.0.401
14.20.1
16.18.0
18.12.0
14.20.1
16.18.0
18.12.0
- actions/setup-node (GitHub Actions)
- Node.js Tool Installer (Azure DevOps)
3.6.12 [PyPy 7.3.3]
3.7.13 [PyPy 7.3.9]
3.8.13 [PyPy 7.3.9]
3.9.12 [PyPy 7.3.9]
3.8.13 [PyPy 7.3.9]
3.9.12 [PyPy 7.3.9]
3.6.15
3.7.14
3.8.14
3.9.14
3.10.7
3.8.14
3.9.14
3.10.7
Platforms affected
Runner images affected
Mitigation ways
If you see any issues with your workflows during this transition period:
For more information you can take a look at the previous announcement here.
The text was updated successfully, but these errors were encountered: