-
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
Small fix to DTDataIntegrityTask.cc #41892
Small fix to DTDataIntegrityTask.cc #41892
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-41892/35832
|
A new Pull Request was created by @perrotta (Andrea Perrotta) for master. It involves the following packages:
@nothingface0, @emanueleusai, @cmsbuild, @pmandrik, @syuvivida, @tjavaid, @micsucmed, @rvenditti can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
Hi, |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-2697da/33036/summary.html Comparison SummarySummary:
|
+1 |
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. @perrotta, @dpiparo, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
The Static Analyzer for DQM/DTMonitorModule/src/DTDataIntegrityTask.cc warns that at line 669 there is a C++ object whose pointer is potentially null
The reason is that the
uROSSummary
(as well as theuROSStatus
) objects are only instantiated whenmode<=2
, while in that line it is accessed for everymode != 1
.Here the check
mode<=2
is extended also to the filling of those Monitor ElementsPR validation:
It builds
No changes expected: at most, the previous version could have crashed if
mode>2