release-tests: use Ubuntu Jammy runner #18712
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Contribution description
We are using Ubuntu Jammy (22.04) with our docker containers to build the release, but the release tests are still run in
ubuntu-latest
, which, at the moment, is still Ubuntu Focal (20.04): https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources. Because of that, both the libasan used and libc used differ between builder and the test runner which leads to an execution error of thenative
binaries. This moves the Github Action runner toubuntu-2204
and installs libasan 6 instead of libasan 5.Testing procedure
I ran the release tests with a representative subset of the tests that are currently failing with master: https://github.com/miri64/RIOT/actions/runs/3209912518/jobs/5246989391 they now succeed. I also started a full run here https://github.com/miri64/RIOT/actions/runs/3209936619/jobs/5247032154, which did not finish yet, but the
not iotlab_creds
tests should still succeed.Issues/PRs references
None.