-
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
removed refs to HLTSchedule
outside of HLTrigger/Configuration
#36073
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-36073/26547
|
A new Pull Request was created by @missirol (Marino Missiroli) for master. It involves the following packages:
@lveldere, @slava77, @Martin-Grunewald, @rekovic, @cecilecaillol, @civanch, @yuanchao, @ahmad3213, @cmsbuild, @missirol, @pmandrik, @emanueleusai, @mdhildreth, @AdrianoDee, @jfernan2, @sbein, @jpata, @pbo0, @francescobrivio, @malbouis, @ssekmen, @srimanob, @rvenditti, @tvami can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-c41939/20433/summary.html Comparison SummarySummary:
|
+alca |
+1 |
+Upgrade Clean up PR, no change is expected. |
+1 |
+hlt |
ping @cms-sw/l1-l2 |
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-c41939/20578/summary.html Comparison SummarySummary:
|
@qliphy maybe we can merge w/o the L1 signature? It's a "minor technical follow-up" after all :) |
merge |
PR description:
This PR is a minor technical follow-up of #35858 related to this comment.
Given the plan to remove the object
HLTSchedule
in the near future (see #35842), the usage ofHLTSchedule
is removed in various configuration files, mostly intest/
folders.PR validation:
Verified that the affected configs are fixed if they were crashing b/c of
HLTSchedule
.Most of these configs are old and already broken anyways for unrelated reasons
(still, references to
HLTSchedule
are removed there too, in the interest of clarity).Unit tests passed.
If this PR is a backport, please specify the original PR and why you need to backport that PR:
N/A