What's with the clang 18 CI failures?

@ednolan you put up some PR’s to fix this in optional as I recall by just removing it – what’s the analysis of the problem?

The Docker images used for CI hadn’t been updated properly in a while due to lack of maintenance. When I updated them, I think what happened is that the version of libstdc++ used for the Clang images was bumped from 14 to 15. Clang 18 apparently has an incompatibility with libstdc++ 15 specifically when used with -std=c++26, so those CI jobs need to be removed now (or I could try and pin libstdc++ to version 14 for those images, but that seems less preferable).

Got it – I guess I’m not worried about clang18 and c++26 since it’s pretty old. Can you drop a pointer to your PR so we can make changes in other repos as needed?

Here’s the commit fixing exemplar: Adjust CI to remove broken Clang 18/C++26/libstdc++ unit test · bemanproject/exemplar@48638ee · GitHub

1 Like