thread-safe

[threus]

Strip thread-safe updates according to request from DQM:
https://hypernews.cern.ch/HyperNews/CMS/get/dqmDevel/2214.html

and removed static variables as suggested by @deguio from #4069

[cmsbuild]

A new Pull Request was created by @threus for CMSSW_7_1_X.

thread-safe

It involves the following packages:

DQM/SiStripMonitorHardware

@ojeda, @danduggan, @rovere, @cmsbuild, @nclopezo, @deguio, @Degano can you please review it and eventually sign? Thanks.
@venturia this is something you requested to watch as well.
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.
@nclopezo, @ktf you are the release manager for this.
You can merge this pull request by typing 'merge' in the first line of your comment.

[cmsbuild]

+1
Tested at: e3d8a02
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-4262/1712/summary.html

[deguio]

+1
it seems to me that these changes make the FEDErrors class thread friendly.
thanks @threus.

[needed for the GR in July]

[cmsbuild]

This pull request is fully signed and it will be integrated in one of the next CMSSW_7_1_X IBs unless changes (tests are also fine). @nclopezo, @ktf can you please take care of it?

[cmsbuild]

Comparison is ready
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-4262/1712/summary.html

[cmsbuild]

This pull request is fully signed and it will be integrated in one of the next CMSSW_7_1_X IBs unless changes (tests are also fine). @nclopezo, @ktf can you please take care of it?

[davidlange6]

@deguio - is this already in 72x?

[deguio]

this is not. when is the automatic PR generated in 72? as soon as this is merged?
I agree that it would be nice to have this tested in some IB before the integration in 71X. several PR are in the same conditions.

[davidlange6]

@deguio - my idea in general was to use 720pre1 for exactly that

[deguio]

@threus could you submit this PR to 72X also?
thank you in advance,
F.