Removed old Timing plugin declaration #4250
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
In the recent change that added a base class to the Timing Service, the old plugin declaration was not removed. This caused two plugin declarations for the same Service to appear and confuses the PluginManager when attempting to load the requested Service.
|
A new Pull Request was created by @Dr15Jones (Chris Jones) for CMSSW_7_2_X. Removed old Timing plugin declaration It involves the following packages: FWCore/Services @cmsbuild, @Degano, @Dr15Jones, @ktf, @nclopezo can you please review it and eventually sign? Thanks. |
|
Bypassing the signatures and approving to the IBs. |
davidlt
added a commit
that referenced
this pull request
Jun 15, 2014
Removed old Timing plugin declaration
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In the recent change that added a base class to the Timing Service, the old plugin declaration was not removed. This caused two plugin declarations for the same Service to appear and confuses the PluginManager when attempting to load the requested Service.