Enable clang-19 testing on CI#27
Merged
neatudarius merged 2 commits intobemanproject:mainfrom Jun 29, 2024
Merged
Conversation
neatudarius
force-pushed
the
experimental/enable-clang-19
branch
from
fe9f1d2 to
4986cbf
Compare
This was referenced Jul 15, 2024
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Enable clang-19 testing on CI ( #1 )
It seems that the previous errors that we had with running clang-19 + Asan are connected to gtest. Check gist:
#10 0x55f30b5bbd1e in __cxx_global_var_init /home/runner/work/Beman.Optional26/Beman.Optional26/src/Beman/Optional26/tests/optional.t.cpp:14:1Literally here we just test gtest :( I also created an executable with a single file (outside the Beman.Optional26 tree) and got the same results.
Found the fix looking through some posts: