-
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
[13_3_X] Run3 era for 2023 PbPb UPC re-reco #43521
[13_3_X] Run3 era for 2023 PbPb UPC re-reco #43521
Conversation
A new Pull Request was created by @stahlleiton (Andre Stahl) for CMSSW_13_3_X. It involves the following packages:
@davidlange6, @miquork, @rappoccio, @sunilUIET, @fabiocos, @cmsbuild, @vlimant, @jfernan2, @antoniovilela, @AdrianoDee, @simonepigazzini, @srimanob, @mandrenguyen can you please review it and eventually sign? Thanks. cms-bot commands are listed here
|
backport of #43378 |
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-0851a2/36377/summary.html Comparison SummarySummary:
|
+1 |
+1 |
+Upgrade |
+pdmv |
+1 |
merge |
@smuzaffar |
This pull request is fully signed and it will be integrated in one of the next CMSSW_13_3_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_14_0_X is complete. This pull request will be automatically merged. |
same reason and it is fixed now. Bot has properly added the |
PR description:
Backport of #43378 which creates a new era "Run3_2023_UPC" meant for the 2023 PbPb UPC re-reco.
PR validation:
Relval workflow 141.901 and private (documented in slides)
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:
Backport from master (14_0_X) to 13_3_X