Update clang CI #2973
Merged
Update clang CI #2973
Conversation
This file contains 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
Unlike before when alpine linux was used for clang-tidy, this tests both libstdc++ and libc++
|
Workflow failed, but the following artifacts are still available for this pull request: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Switches the clang tidy workflow to use arch linux instead of alpine linux. I added back the alpine linux compilations in a new ci job, which compiles with both
libstdc++andlibc++.When looking through this I remembered there was the
util/run-clang-tidy.pyandutil/clang-tidy.shscripts meant to help locally. You can runutil/clang-tidy.shfrom within the build directory which should be identical to how it runs in CI.Last I checked the meson
clang-tidytarget didn't parallelize very well, but maybe that has been improved and we can remove some of these scripts.