-
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
Update 2024 MC GTs with the L1 menu L1Menu_Collisions2024_v1_0_1_xml #44389
Conversation
cms-bot internal usage |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-44389/39450
|
A new Pull Request was created by @perrotta for master. It involves the following packages:
@consuegs, @cmsbuild, @perrotta, @saumyaphor4252 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
@cmsbuild, please abort |
@saumyaphor4252 please re-read #44054 (comment) :) |
Just a heads up, we'd need a backport to 14_0 as well. Thanks you! |
@cms-sw/alca-l2 as #44054 is looking conveged, can you provide versioned full-fledged GlobalTags here? |
dc57599
to
f9ce6b7
Compare
Given the succesfull tests of the Candidate GTs together with #44054, candidate GTs have been transformed into (identical, see diffs below) versioned GTs:
The PR description was modified taking into account the versioned GTs |
please test with #44054 |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-44389/39469
|
Pull request #44389 was updated. @perrotta, @consuegs, @saumyaphor4252 can you please check and sign again. |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-97c3de/38120/summary.html Comparison SummarySummary:
|
+alca
|
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, @sextonkennedy, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
REMINDER @sextonkennedy, @antoniovilela, @rappoccio: This PR was tested with #44054, please check if they should be merged together |
+1 |
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-0-1/36759
The updated tag for L1TUtmTriggerMenuRcd is
From: L1Menu_Collisions2024_v1_0_0_xml
To: L1Menu_Collisions2024_v1_0_1_xml
GT differences
phase1_2024_design: https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/140X_mcRun3_2024_design_v4/140X_mcRun3_2024_design_v3
phase1_2024_realistic: https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/140X_mcRun3_2024_realistic_v5/140X_mcRun3_2024_realistic_v4
phase1_2024_cosmics:https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/140X_mcRun3_2024cosmics_realistic_deco_v5/140X_mcRun3_2024cosmics_realistic_deco_v4
phase1_2024_cosmics_design: https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/140X_mcRun3_2024cosmics_design_deco_v3/140X_mcRun3_2024cosmics_design_deco_v2
PR validation:
This must be tested (and merged) together with #44054
bot tests with the former Candidate GTs, identical to the versioned GTs now in the PR, were succesful, see #44054 (comment)
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
This will have to be backported in 14_0_X