-
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
Update muon (un)packer with support for fixed uGMT firmware #41844
Update muon (un)packer with support for fixed uGMT firmware #41844
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-41844/35745
|
A new Pull Request was created by @dinyar (Dinyar Rabady) for master. It involves the following packages:
@epalencia, @cmsbuild, @aloeliger can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
Please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-f3b4db/32934/summary.html Comparison SummarySummary:
|
@dinyar I think a port to 13_1 is not a terrible, as per the release notes:
I think better safe than forgotten in case of need in this scenario for a small change. |
+l1 |
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, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
Update to the muon unpacker to support a coming uGMT firmware version that places the two loose muon shower bit on a different link. The change is necessary due to a miscommunication between uGT and uGMT teams.
This should go to P5, so I plan on making a backport to 13_0_X, however could you let me know if a packport to 13_1_X is also necessary?
PR validation:
Ran standard tests.