-
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
use --hltProcess reHLT
in Run-3 Data RelVals [12_5_X
]
#39899
use --hltProcess reHLT
in Run-3 Data RelVals [12_5_X
]
#39899
Conversation
A new Pull Request was created by @missirol (Marino Missiroli) for CMSSW_12_5_X. It involves the following packages:
@bbilin, @cmsbuild, @AdrianoDee, @srimanob, @kskovpen, @sunilUIET can you please review it and eventually sign? Thanks. cms-bot commands are listed here
|
test parameters:
|
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-0c58fe/28596/summary.html Comparison SummaryThe workflows 140.002, 140.001, 139.004, 139.003, 139.002, 139.001 have different files in step1_dasquery.log than the ones found in the baseline. You may want to check and retrigger the tests if necessary. You can check it in the "files" directory in the results of the comparisons @slava77 comparisons for the following workflows were not done due to missing matrix map:
Summary:
|
+pdmv |
+Upgrade |
This pull request is fully signed and it will be integrated in one of the next CMSSW_12_5_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_12_6_X is complete. This pull request will now be reviewed by the release team before it's merged. @perrotta, @dpiparo, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
@missirol could you please add a few lines in the PR description that can explain the difference between the PR merged in master, and the two backports in 12_4 and 12_5, and the differences betwee the two backports themselves? |
Description updated. Indeed, the backports are not verbatim (and had to be done manually), because The net result of these 3 PRs, though, is the same: add Each of these 3 PRs was done as follows:
|
+1
|
backport of #39834
PR description:
From the description of #39834:
To add
--hltProcess reHLT
to the post-HLT step of the Run-3 data RelVals, the following is done:HLTDR3_2021
toHLTDR3_2022
;HLTRUN3
withHLTDR3_2022
(they are identical, making the first redundant);RECODR3_reHLT
(="RECODR3 + --hltProcess=reHLT"
);RECODR3_2021
withRECODR3_reHLT
;RECONANORUN3
toRECONANORUN3_reHLT
, and base it off ofRECODR3_reHLT
;RECOCOSMRUN3
toRECOCOSMRUN3_reHLT
.This backport is not verbatim due to differences in
relval_{steps,standard}.py
across different release cycles.PR validation:
runTheMatrix.py -l 139.001,140.001
passed.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:
#39834
Fix to Run-3 Data RelVal wfs involving HLT.