-
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
add a phase-2 D110 relval workflow running the HLT timing menu, up to step2 #45776
Conversation
cms-bot internal usage |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-45776/41498
|
A new Pull Request was created by @mmusich for master. It involves the following packages:
@AdrianoDee, @cmsbuild, @kskovpen, @miquork, @srimanob, @subirsarkar, @sunilUIET can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@cmsbuild, please test |
-1 Failed Tests: RelVals-INPUT
RelVals-INPUT
Expand to see more relval errors ...
Comparison SummarySummary:
|
please test with #45774 |
+1 Size: This PR adds an extra 12KB to repository Comparison SummarySummary:
|
+pdmv |
+Upgrade |
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. @mandrenguyen, @rappoccio, @sextonkennedy, @antoniovilela (and backports should be raised in the release meeting by the corresponding L2) |
Milestone for this pull request has been moved to CMSSW_14_2_X. Please open a backport if it should also go in to CMSSW_14_1_X. |
+1 |
PR description:
Title say is all: introduce a phase-2 D110-based relval workflow running the HLT timing menu, up to step2 (in order to be fast) and included in the limited matrix. This is done in order to spot whenever the phase-2 HLT timing menu configuration gets broken.
PR validation:
runTheMatrix.py --what upgrade -l 29634.75 -t 4 -j 8
runs fine, when this branch is tested in conjunction with #45768.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:
N/A