-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Run3-Sim101F Avoid compilation warnings in some of the codes of Validation/RecoTau #36608
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-36608/27582
|
A new Pull Request was created by @bsunanda (Sunanda Banerjee) for master. It involves the following packages:
@emanueleusai, @ahmad3213, @cmsbuild, @jfernan2, @pmandrik, @pbo0, @rvenditti can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@cmsbuild Please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-54a768/21494/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, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
@@ -21,7 +21,7 @@ | |||
#include <vector> | |||
#include <string> | |||
|
|||
class TauDQMFileLoader : public edm::EDAnalyzer { | |||
class TauDQMFileLoader : public edm::one::EDAnalyzer<edm::one::WatchRuns> { | |||
typedef dqm::legacy::DQMStore DQMStore; | |||
typedef dqm::legacy::MonitorElement MonitorElement; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is the direct use of DQMStore
safe in non-legacy modules?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe it is not. I leave the author of the code to make use of DQM codes``
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Then, to me, it would make more sense to leave these modules as legacy and migrate them properly (or remove) later rather than enabling unsafe code.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done that
@@ -27,14 +27,15 @@ | |||
|
|||
using namespace std; | |||
|
|||
class DQMHistNormalizer : public edm::EDAnalyzer { | |||
class DQMHistNormalizer : public edm::one::EDAnalyzer<edm::one::WatchRuns> { | |||
public: | |||
typedef dqm::legacy::DQMStore DQMStore; | |||
typedef dqm::legacy::MonitorElement MonitorElement; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This module appears to use DQMStore directly too.
@@ -24,7 +24,7 @@ | |||
#include <vector> | |||
#include <map> | |||
|
|||
class TauDQMHistPlotter : public edm::EDAnalyzer { | |||
class TauDQMHistPlotter : public edm::one::EDAnalyzer<edm::one::WatchRuns> { | |||
typedef dqm::legacy::DQMStore DQMStore; | |||
typedef dqm::legacy::MonitorElement MonitorElement; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same here.
@@ -19,7 +19,7 @@ | |||
|
|||
#include <string> | |||
|
|||
class TauDQMSimpleFileSaver : public edm::EDAnalyzer { | |||
class TauDQMSimpleFileSaver : public edm::one::EDAnalyzer<> { | |||
public: | |||
typedef dqm::legacy::DQMStore DQMStore; | |||
typedef dqm::legacy::MonitorElement MonitorElement; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
And here.
@cmsbuild Please test |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-36608/27632
|
Pull request #36608 was updated. @emanueleusai, @ahmad3213, @jfernan2, @rvenditti, @pbo0, @pmandrik can you please check and sign again. |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-54a768/21531/summary.html CMS StaticAnalyzer warnings: There are 4 inherits from legacy modules warnings. See https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-54a768/21531/llvm-analysis/legacy-mod-sa.txt for details. Comparison SummarySummary:
|
Do we understand why now we get these CMS StaticAnalyzer warnings and in previous test/changes not? |
I guess those get reported because this PR touches those files. Those changes are not visible in the diff because one commit makes the change, and a later commit undoes those changes. It would be better to squash the commits into one, and maybe change the title of the PR to something along "Remove some unnecessary header includes". |
@jfernan2 Can you sign this - we need to fix the other DQM codes later |
+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, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
+1
|
PR description:
Avoid compilation warnings in some of the codes of Validation/RecoTau
PR validation:
Use the runTheMatrix test workflows
if this PR is a backport please specify the original PR and why you need to backport that PR:
Nothing special