-
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
Add GEM channel and strip payload dump utilities #44460
Add GEM channel and strip payload dump utilities #44460
Conversation
cms-bot internal usage |
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-44460/39540
Code check has found code style and quality issues which could be resolved by applying following patch(s)
|
9782ffb
to
760f7be
Compare
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-44460/39541
|
A new Pull Request was created by @saumyaphor4252 for master. It involves the following packages:
@perrotta, @francescobrivio, @cmsbuild, @consuegs, @saumyaphor4252 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@cmsbuild please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-c56700/38251/summary.html Comparison SummarySummary:
|
+db
|
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. @antoniovilela, @rappoccio, @sextonkennedy (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
The PR adds the following three records to
CondCore/Utilities
scripts to dump the payload content. The relevant CMS Talk post is [1].The first record is already in the GTs and the latter 2 will be needed in the online GTs to allow strip masking in [2].
[1] https://cms-talk.web.cern.ch/t/request-for-2024-data-taking-from-gem/36149
[2] #44085
FYI @yeckang
PR validation:
Following commands now run
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:
Not a backport.