-
Notifications
You must be signed in to change notification settings - Fork 264
Make static analyzer errors more visible #2495
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
A new Pull Request was created by @iarspider for branch master. @cmsbuild, @iarspider, @smuzaffar can you please review it and eventually sign? Thanks. |
|
cms-bot internal usage |
|
please test with cms-sw/cmssw#48035 |
|
@iarspider , can you please open a cmssw draft PR to test this? My try of cms-sw/cmssw#48035 did not work |
@iarspider ?? |
|
I am looking into it - I need to figure out how to make clang analyzer report an error (all of it's diagnostics are emitted as warnings, not errors). |
|
please test with cms-sw/cmssw#48065 |
|
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-faf788/46127/summary.html
Comparison SummarySummary:
|
see cms-sw/cmssw#48065 + test results in #2495 (comment) |
|
thanks @iarspider Looks like we can use |
|
+externals This could go in, @iarspider open a new PR for highlighting error message in different color |
|
This pull request is fully signed and it will be integrated in one of the next master IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @rappoccio, @antoniovilela, @sextonkennedy, @mandrenguyen (and backports should be raised in the release meeting by the corresponding L2) |
No description provided.