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
Remove deprecated EventSetup get functions #40427
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-40427/33559
|
A new Pull Request was created by @wddgit (W. David Dagenhart) for master. It involves the following packages:
@cmsbuild, @smuzaffar, @Dr15Jones, @makortel can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
-1 Failed Tests: HeaderConsistency Comparison SummarySummary:
|
@wddgit As far as I can tell |
I just submitted PR #40431 that deletes SCRegressionCalculator.h. |
please test with #40519 #40431 was just merged so lets try the tests again. That should fix the header check failure. Note #40519 is completely unrelated and independent of this one. It does not matter whether it is merged first or not. I just wanted the unit test it fixes to pass when the PR tests run. |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-eb4e69/29979/summary.html Comparison SummaryThere are some workflows for which there are errors in the baseline: Summary:
|
+1 |
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. @perrotta, @dpiparo, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
Remove deprecated EventSetup get functions. These are the ones that do not use a token. This code has been deprecated for a while and previously a lot of work has been done by many people to remove all the code that depended on the code deleted by this PR.
PR validation:
This is almost exclusively deletions. The fact that it successfully builds after running checkdeps eliminates almost all possibilities for errors. I also ran unit tests for FWCore/Framework and FWCore/Integration locally.