Skip to content

Fix CI after Debian image changes - #157

Merged
joto merged 1 commit into
masterfrom
kk/fix-ci-images
Oct 13, 2026
Merged

joto merged 1 commit into
masterfrom
kk/fix-ci-images

Conversation

@kkaefer

@kkaefer kkaefer commented Oct 8, 2026 •

Copy link
Copy Markdown
Member

Fixes the CI failures seen on #156, which are unrelated to that change:

  • bullseye: LTS ended 2026-08-31 and its packages now 404 on the main mirrors. Dropped from the CI jobs (along with the long-disabled sanitizer entry that referenced it). ubuntu:20.04 (gcc 9, clang 10, cmake 3.16) still covers older compilers than bullseye did.
  • big-endian: debian:bookworm has no s390x image; switch to debian:trixie.
  • clang-tidy: debian:testing now ships clang 22 and debian:experimental clang 24; bump to those. This also needs g++ installed so clang finds a matching libstdc++, clang-tidy-21 to -24 added to the lookup in CMakeLists.txt, and -Wno-c2y-extensions because clang 22 rejects Catch's __COUNTER__ under -Werror.

Overall though, I'm wondering whether we should we move away from Debian experimental since it's a moving target?

@kkaefer
kkaefer requested a review from a team as a code owner October 8, 2026 09:40
Drop debian:bullseye, whose LTS ended on 2026-08-31 and whose packages are gone from the main mirrors. ubuntu:20.04 still covers the oldest compilers.

Run the s390x big-endian job on debian:trixie, because debian:bookworm has no s390x image.

Update the clang-tidy job for the clang versions that debian:testing (22) and debian:experimental (24) now ship:
- Install g++ so clang finds a matching libstdc++.
- Let CMake find clang-tidy-21 through clang-tidy-24.
- Pass -Wno-c2y-extensions, since clang 22 rejects Catch's __COUNTER__ under -Werror.
@kkaefer
kkaefer requested a review from joto October 8, 2026 12:40
@kkaefer
kkaefer added this pull request to stack #158 October 8, 2026 12:44
@joto

joto commented Oct 13, 2026

Copy link
Copy Markdown
Collaborator

Overall though, I'm wondering whether we should we move away from Debian experimental since it's a moving target?

I don't necessarily see a failure in Debian experimental as something that would block me from merging any changes.
I use it more as a "canary in the coalmine" to see early if errors might crop up due to bleeding edge compiler versions that will probably affect us down the line. So it is occasionally useful, especially before doing releases, to make sure the shiny new release will not break ten days later due to some new compiler warning or so.

@joto
joto merged commit 219c329 into master Oct 13, 2026
66 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants