Fix problems with prefetch and ConcurrentModuleTimer #3578
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
If data was being prefetched for a module it could cause an assert for ConcurrentModuleTimer to fail. The problem was the Service was trying to 'stop' its clock when there was not a running module.
|
A new Pull Request was created by @Dr15Jones (Chris Jones) for CMSSW_7_1_X. Fix problems with prefetch and ConcurrentModuleTimer It involves the following packages: FWCore/Services @cmsbuild, @Degano, @Dr15Jones, @ktf, @nclopezo can you please review it and eventually sign? Thanks. |
|
+1 |
ktf
added a commit
that referenced
this pull request
Apr 30, 2014
…eTimer Multithreading -- Fix problems with prefetch and ConcurrentModuleTimer
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.
If data was being prefetched for a module it could cause an assert
for ConcurrentModuleTimer to fail. The problem was the Service was
trying to 'stop' its clock when there was not a running module.