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
Delete legacy OutputModule base class #29633
Conversation
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-29633/15013
|
A new Pull Request was created by @wddgit (W. David Dagenhart) for master. It involves the following packages: DQMServices/FwkIO @smuzaffar, @andrius-k, @Dr15Jones, @makortel, @schneiml, @cmsbuild, @kmaeshima, @jfernan2, @fgolf, @fioriNTU, @santocch, @peruzzim can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
The tests are being triggered in jenkins. |
Interesting discovery about the |
-1 Tested at: 941d584 CMSSW: CMSSW_11_1_X_2020-05-04-1100 I found follow errors while testing this PR Failed tests: UnitTests
I found errors in the following unit tests: ---> test TestFWCoreServicesDriver had ERRORS |
Comparison job queued. |
Is this the real error in the unit test?
I.e. strack trace generation took too long in the zombie killer test? |
Comparison is ready Comparison Summary:
|
@cmsbuil, please test Let's try again |
+1 |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
+1 |
+1 |
+xpog |
+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. @silviodonato, @dpiparo (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
Delete the legacy output module base class and all references to it. Already, nothing was inheriting from it anymore. A few classes were still using its fillDescription function, but I moved them to use the corresponding function from the one::OutputModule and with the changes included here that function should be doing exactly the same thing.
PR validation:
Existing Core unit tests pass. There is no new functionality. Nothing should change. There will just be less code to maintain.