Skip to content
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

Don't update global registries in secondary source #1034

Merged
merged 1 commit into from
Oct 9, 2013

Conversation

wmtan
Copy link
Contributor

@wmtan wmtan commented Oct 9, 2013

The parameter set and parentage registries are each globals across all threads. This pull request ensures that a secondary input source will not update either of them. This is needed for thread safety.
This has been successfully tested with the full relval matrix.

@cmsbuild
Copy link
Contributor

cmsbuild commented Oct 9, 2013

A new Pull Request was created by @wmtan for CMSSW_7_0_X.

Don't update global registries in secondary source

It involves the following packages:

IOPool/Input

@smuzaffar, @Dr15Jones, @ktf, @nclopezo can you please review it and eventually sign? Thanks.
You can sign-off by replying to this message having '+1' in the first line of your reply.
You can reject by replying to this message having '-1' in the first line of your reply.
@ktf you are the release manager for this.

@nclopezo
Copy link
Contributor

nclopezo commented Oct 9, 2013

@Dr15Jones
Copy link
Contributor

+1

@cmsbuild
Copy link
Contributor

cmsbuild commented Oct 9, 2013

This pull request is fully signed and it will be integrated in one of the next IBs unless changes or unless it breaks tests. @ktf can you please take care of it?

ktf added a commit that referenced this pull request Oct 9, 2013
Multithreaded framework -- Don't update global registries in secondary source
@ktf ktf merged commit ecc0b4a into cms-sw:CMSSW_7_0_X Oct 9, 2013
@wmtan wmtan deleted the NoGlobalUpdatesInSecondarySource branch October 11, 2013 17:11
bundocka pushed a commit to bundocka/cmssw that referenced this pull request Aug 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants