-
Notifications
You must be signed in to change notification settings - Fork 97
Update from Ubuntu 18 (gcc-6, clang-6) to Ubuntu 20 (gcc-7, clang-6) [AP-3178] #1473
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
Ubuntu 18 is EOL since May 2023. The gcc 6 compiler is not explicitly required by any of our customers. This change updates the stage to Ubuntu 24 and gcc 14 / clang 18.
{ c: "clang-6.0", cxx: "clang++-6.0", package: "clang-6.0" } | ||
] | ||
build_shared_libraries: [ true, false ] | ||
exclude: [ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I digged in the history and this combination was excluded because at some point, there was a "code coverage" job that covered this combination. This job is not existing anymore, so I'm adding the combination again.
f624dfc
to
6fc1396
Compare
6fc1396
to
8e7e48f
Compare
|
@sbmueller Ubuntu 20 will EOL in April this year. Would it be worth it to try to bump it to 22 or 24? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good for me! Only point is the comment above.
Description
@swift-nav/algint-team
This PR updates the C stages in the CI from relying on Ubuntu 18 (gcc-6, clang-6) to Ubuntu 20 (gcc-7, clang-6). Ubuntu 18 is EOL since May 2023. Recently, we observed issues, e.g. in GitHub Actions due to old versions of GLIBC in Ubuntu 18 jobs. We decided to not further invest time and energy in maintaining these old pipelines, because:
libsbp
.API compatibility
Does this change introduce a API compatibility risk?
No, there are no changes to the code.
API compatibility plan
If the above is "Yes", please detail the compatibility (or migration) plan:
JIRA Reference
https://swift-nav.atlassian.net/browse/AP-3178