Skip to content

Use Clang 19 instead of 16 in CI#934

Merged
tmadlener merged 1 commit intomasterfrom
update-clang-lcg
Feb 16, 2026
Merged

Use Clang 19 instead of 16 in CI#934
tmadlener merged 1 commit intomasterfrom
update-clang-lcg

Conversation

@jmcarcell
Copy link
Member

BEGINRELEASENOTES

  • Use Clang 19 instead of 16 in CI, since these builds are going to be revomed

ENDRELEASENOTES

Clang 16 builds seem not to work and are going to be removed, see
https://its.cern.ch/jira/projects/SPI/issues/SPI-2955.

Clang 16 builds seem not to work and are going to be removed, see
https://its.cern.ch/jira/projects/SPI/issues/SPI-2955
@tmadlener
Copy link
Collaborator

tmadlener commented Feb 16, 2026

Is this the only use of clang16 that we have in the podio CI?

@tmadlener tmadlener enabled auto-merge (squash) February 16, 2026 09:36
@tmadlener tmadlener merged commit bb40078 into master Feb 16, 2026
29 checks passed
@tmadlener tmadlener deleted the update-clang-lcg branch February 16, 2026 09:48
@jmcarcell
Copy link
Member Author

I think so, otherwise it would not pass with Clang 16.

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