-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
[Core] Mark cms::Exception and edm::Exception functions that throw exceptions as noreturn #46388
[Core] Mark cms::Exception and edm::Exception functions that throw exceptions as noreturn #46388
Conversation
…ceptions as noreturn
cms-bot internal usage |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-46388/42235 |
A new Pull Request was created by @iarspider for master. It involves the following packages:
@Dr15Jones, @cmsbuild, @makortel, @smuzaffar can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
test parameters:
|
please test |
-1 Failed Tests: Build BuildI found compilation warning when building: See details on the summary page. |
please test |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-46388/42247 |
Pull request #46388 was updated. @Dr15Jones, @makortel, @smuzaffar can you please check and sign again. |
+1 Size: This PR adds an extra 20KB to repository Comparison SummarySummary:
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-46388/42270 |
Pull request #46388 was updated. @Dr15Jones, @makortel, @smuzaffar can you please check and sign again. |
-1 Failed Tests: UnitTests Unit TestsI found 1 errors in the following unit tests: ---> test test_SiStripG2GainsValidator had ERRORS Comparison SummarySummary:
|
Comparison differences are related to #46416 |
+core |
This pull request is fully signed and it will be integrated in one of the next master IBs (test failures were overridden). 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) |
Do we know why the warning wasn't flagged by the PR test machinery? |
+1 |
@makortel , bot flags only those warnings which are coming from files touched by the PR. In this case warning was coming from |
Sounds good, thanks. |
PR description:
This should hopefully solve LLVM analyzer warnings like this: link
PR validation:
Bot tests