-
Notifications
You must be signed in to change notification settings - Fork 4.4k
Fix cfi
creation for conf db parsing
#47156
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
type bug-fix |
cms-bot internal usage |
urgent
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-47156/43386 |
A new Pull Request was created by @mmusich for master. It involves the following packages:
@cmsbuild, @jfernan2, @mandrenguyen can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@cmsbuild, please test |
+1 Size: This PR adds an extra 24KB to repository 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. @sextonkennedy, @rappoccio, @antoniovilela, @mandrenguyen (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
@Martin-Grunewald reported an issue in the confDB parsing of
CMSSW_15_0_0_pre2
concerning:this is due to #47017 and #47045 having the modules
ConcreteChargedCandidateProducer
andCSCSegmentProducer
auto-generate cfi files with incomplete top level parameter configurations.This PR fixes the issue
PR validation:
Upon compilation I get the following python files available:
and
which is fine for parsing purposes.
If this PR is a backport please specify the original PR and why you need to backport that PR. If this PR will be backported please specify to which release cycle the backport is meant for:
N/A