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
create cfi
files for JetConstituentSelector<>
plugins
#37039
create cfi
files for JetConstituentSelector<>
plugins
#37039
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-37039/28472
|
A new Pull Request was created by @missirol (Marino Missiroli) for master. It involves the following packages:
@jpata, @cmsbuild, @clacaputo, @slava77 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
please abort The 1 error in the The tests seem stuck anyways, so I will restart them with the fix in #37038. |
please test with #37038 |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-543250/22622/summary.html Comparison SummarySummary:
|
assign hlt for bookkeeping purposes |
New categories assigned: hlt @missirol,@Martin-Grunewald you have been requested to review this Pull request/Issue and eventually sign? Thanks |
+hlt
|
+reconstruction
|
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:
This PR is technical. It enables the creation of default
cfi
files for all instances of the plugin templateJetConstituentSelector
.This is expected to have no consequences for any existing workflow.
The reason to enable the creation of the said
cfi
files is that an external tool used by HLT (i.e.ConfDB
) relies on the existence ofcfi
files to know the default configuration of CMSSW plugins.Thanks to @rgerosa for reporting the issue.
Merely technical. No changes expected.
PR validation:
The new
cfi
files are created as expected.If this PR is a backport, please specify the original PR and why you need to backport that PR:
N/A