-
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
[14.0.X] Update 2024 MC GTs with the L1 menu #44080
[14.0.X] Update 2024 MC GTs with the L1 menu #44080
Conversation
A new Pull Request was created by @mmusich for CMSSW_14_0_X. It involves the following packages:
@saumyaphor4252, @cmsbuild, @perrotta, @consuegs can you please review it and eventually sign? Thanks. cms-bot commands are listed here
|
cms-bot internal usage |
test parameters:
|
@cmsbuild, please test |
Thank you @mmusich for having anticipated it (I was going to do the same, but being leaving to take the train to Geneve it would have taken a bit more time) |
REMINDER @sextonkennedy, @antoniovilela, @rappoccio: This PR was tested with #44074, please check if they should be merged together |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-3ce1e1/37673/summary.html Comparison SummarySummary:
|
urgent |
+alca |
This pull request is fully signed and it will be integrated in one of the next CMSSW_14_0_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_14_1_X is complete. This pull request will now be reviewed by the release team before it's merged. @antoniovilela, @sextonkennedy, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
backport of #44078
PR description:
Update the 2024 MC GTs with the new L1 menu as in cmsTalk https://cms-talk.web.cern.ch/t/update-of-the-2024-l1-menu-tag-l1menu-collisions2024-v1-1-0/35509
The updated tag for L1TUtmTriggerMenuRcd is
From: L1Menu_Collisions2023_v1_2_0_xml
To: L1Menu_Collisions2024_v1_0_0_xml
GT differences:
PR validation:
This must be tested (and merged) together with #44074.
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:
verbatim backport of #44078