-
Notifications
You must be signed in to change notification settings - Fork 4.4k
[15_0_X] Fix the AlCaRecoTriggerBits/SecondaryDataset tag for the first IOVs in Run2 and Run3 data GT #47871
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
[15_0_X] Fix the AlCaRecoTriggerBits/SecondaryDataset tag for the first IOVs in Run2 and Run3 data GT #47871
Conversation
…n Run2 and Run3 data GT
A new Pull Request was created by @perrotta for CMSSW_15_0_X. It involves the following packages:
@atpathak, @cmsbuild, @consuegs, @perrotta can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
cms-bot internal usage |
backport of #47839 |
please test |
+1 Size: This PR adds an extra 16KB to repository Comparison SummarySummary:
|
+alca |
This pull request is fully signed and it will be integrated in one of the next CMSSW_15_0_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_15_1_X is complete. This pull request will now be reviewed by the release team before it's merged. @sextonkennedy, @antoniovilela, @rappoccio, @mandrenguyen (and backports should be raised in the release meeting by the corresponding L2) |
REMINDER @rappoccio, @sextonkennedy, @mandrenguyen, @antoniovilela: This PR was tested with #47816, please check if they should be merged together |
+1 |
PR description:
Fix the AlCaRecoTriggerBits/SecondaryDataset tag for the first IOVs in Run2 and Run3 data GT
Modified GTs in autoCond:
'run2_data' : 141X_dataRun2_v3
'run3_data' : 150X_dataRun3_v4
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:
backport of #47839