Add clazy Qt static analysis to the clang-tidy workflow#14260
Open
magnesj wants to merge 1 commit into
Open
Conversation
Build clazy 1.15 from source against the installed clang/llvm-19 (the packaged clazy is built against an older Clang that cannot parse libstdc++-14's C++23 headers), then run clazy-standalone over the existing compile_commands.json as a non-blocking, report-only step. Analysis runs one process per file across all cores. The two highest -volume checks (range-loop-detach, non-pod-global-static) are excluded to surface higher-signal Qt findings, and ApplicationLibCode/UnitTests is skipped because gtest is only fetched for the test target and its headers are absent on this configure-only tree.
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
1 participant
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.
Adds clazy (Qt-oriented static analyzer) to the existing
clang-tidyworkflow as a non-blocking, report-only step.What it does
compile_commands.json.clazy-standaloneover the existingcompile_commands.json, one process per file across all cores.range-loop-detach,non-pod-global-static) to surface higher-signal Qt findings.ApplicationLibCode/UnitTestsbecause gtest is only fetched for the test target and its headers are absent on this configure-only tree.The step is
continue-on-error: true— it reports Qt findings in the log and never fails the run or modifies files.