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
Subdirectories for GEM-CSC LUTs #33677
Subdirectories for GEM-CSC LUTs #33677
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-33677/22579
|
A new Pull Request was created by @dildick (Sven Dildick) for master. It involves the following packages: L1Trigger/CSCTriggerPrimitives @cmsbuild, @rekovic, @cecilecaillol can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
-1 Failed Tests: RelVals RelVals-INPUT AddOn RelVals
RelVals-INPUT
Expand to see more relval errors ...
AddOn Tests
|
Hi @cecilecaillol. Sorry I should have clarified. Could you test again with cms-data/L1Trigger-CSCTriggerPrimitives#8? |
please test with cms-data/L1Trigger-CSCTriggerPrimitives#8 |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-fcefa3/14973/summary.html Comparison SummarySummary:
|
+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. @silviodonato, @dpiparo, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
@cms-sw/l1-l2 please also check and sign cms-data/L1Trigger-CSCTriggerPrimitives#8 |
+1 |
PR description:
GEM-CSC LUTs are being organized into subdirectories
This should fix the issue in cms-data/L1Trigger-CSCTriggerPrimitives#8
PR validation:
Code compiles.
if this PR is a backport please specify the original PR and why you need to backport that PR:
N/A
Before submitting your pull requests, make sure you followed this checklist: