-
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
Bug fix: initialization of genJetMatch token in appropriate place #45802
Bug fix: initialization of genJetMatch token in appropriate place #45802
Conversation
cms-bot internal usage |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-45802/41541 |
A new Pull Request was created by @mbluj for master. It involves the following packages:
@cmsbuild, @ftorrresd, @hqucms, @jfernan2, @mandrenguyen, @vlimant can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
enable nano |
please test |
+1 Size: This PR adds an extra 24KB to repository Comparison SummarySummary:
NANO Comparison SummarySummary:
Nano size comparison Summary:
|
+1 |
Milestone for this pull request has been moved to CMSSW_14_2_X. Please open a backport if it should also go in to CMSSW_14_1_X. |
+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. @rappoccio, @mandrenguyen, @sextonkennedy, @antoniovilela (and backports should be raised in the release meeting by the corresponding L2) |
Please confirm that it should be backported to 14_1 and 14_0. |
Yes please make the backport. Thank you! |
type bug-fix, jetmet |
+1 |
PR description:
As title says: this PR moves initialization of the
genJetMatchToken
to a correct place which fixes a bug.This bug have not manifested until now as gen-matching is not used in central workflows.
PR validation:
Validated in a custom workflow with and without enabling gen-matching.
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:
This probably should be backported to 14_0 series although the gen-matching is disabled in central workflows.