-
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
fixes leftover from #45636 #45768
fixes leftover from #45636 #45768
Conversation
cms-bot internal usage |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-45768/41482 |
A new Pull Request was created by @mmusich for master. It involves the following packages:
@Martin-Grunewald, @cmsbuild, @mmusich can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@cmsbuild, please test |
048e0c2
to
6524606
Compare
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-45768/41495 |
Pull request #45768 was updated. @Martin-Grunewald, @cmsbuild, @mmusich can you please check and sign again. |
enable hlt_p2_timing |
@cmsbuild, please test |
type bug-fix |
-1 Failed Tests: RelVals-INPUT
RelVals-INPUT
Expand to see more relval errors ...
Comparison SummarySummary:
|
@cmsbuild ignore tests-rejected with ib-failure |
+hlt
|
This pull request is fully signed and it will be integrated in one of the next master IBs (test failures were overridden). This pull request will now be reviewed by the release team before it's merged. @mandrenguyen, @antoniovilela, @sextonkennedy, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
For the record, the phase2 timing monitoring works again as of CMSSW_14_1_X_2024-08-23-2300. |
PR description:
quick followup from #45636
hlt
(HLT
) label to Phase-2 HLT modules (sequences) #45636 (comment)PR validation:
Run the following script to test the phase-2 timing menu:
No regression expected as this product should not be consumed in the menu, see #45636 (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 please specify to which release cycle the backport is meant for:
N/A