-
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
Backport to 12_3_X for CSC unpacking update PR#37279 #37479
Backport to 12_3_X for CSC unpacking update PR#37279 #37479
Conversation
A new Pull Request was created by @barvic (Victor Barashko) for CMSSW_12_3_X. It involves the following packages:
@jpata, @cmsbuild, @clacaputo, @slava77 can you please review it and eventually sign? Thanks. cms-bot commands are listed here
|
backport of #37279 |
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-5e31e5/23684/summary.html Comparison SummarySummary:
|
"Removing the +1 here: I did not notice that it still misses the reco signature"
|
Dear @clacaputo, could you please review and sign this back-port, so @perrotta could proceed with merging this PR to 12_3_X and then it could be available for P5 deployment? |
+reconstruction
|
This pull request is fully signed and it will be integrated in one of the next CMSSW_12_3_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_12_4_X is complete. 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:
Backport to 12_3_X for CSC unpacking update PR #37279
if this PR is a backport please specify the original PR and why you need to backport that PR:
Would need to have those unpacking updates deployed at P5 soon as possible for proper unpacking of CSC ALCT/(O)TMB data with new versions of firmware with enabled Run3 features