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
Fix thread safety issue in FEDNumbering #26321
Conversation
Removed the thread unsafe initialization of static member data. Change to initialize the data either at compile time (via the use of constexpr) or at shared library load time.
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-26321/9024
|
A new Pull Request was created by @Dr15Jones (Chris Jones) for master. It involves the following packages: DataFormats/FEDRawData @mommsen, @cmsbuild, @emeschi can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
The tests are being triggered in jenkins. |
-1 Tested at: 376d5cb You can see the results of the tests here: I found follow errors while testing this PR Failed tests: Build HeaderConsistency
I found compilation error when building: >> Compiling /build/cmsbld/jenkins/workspace/ib-any-integration/CMSSW_10_6_X_2019-04-02-1100/src/EventFilter/SiStripRawToDigi/src/SiStripFEDBufferComponents.cc >> Compiling /build/cmsbld/jenkins/workspace/ib-any-integration/CMSSW_10_6_X_2019-04-02-1100/src/EventFilter/SiStripRawToDigi/src/SiStripDetSetVectorFiller.cc >> Compiling /build/cmsbld/jenkins/workspace/ib-any-integration/CMSSW_10_6_X_2019-04-02-1100/src/EventFilter/SiStripRawToDigi/src/SiStripFEDBuffer.cc In file included from /build/cmsbld/jenkins/workspace/ib-any-integration/CMSSW_10_6_X_2019-04-02-1100/src/EventFilter/SiStripRawToDigi/interface/SiStripFEDBufferGenerator.h:5:0, from /build/cmsbld/jenkins/workspace/ib-any-integration/CMSSW_10_6_X_2019-04-02-1100/src/EventFilter/SiStripRawToDigi/src/SiStripFEDBufferGenerator.cc:1: /build/cmsbld/jenkins/workspace/ib-any-integration/CMSSW_10_6_X_2019-04-02-1100/src/EventFilter/SiStripRawToDigi/interface/SiStripFEDBufferComponents.h:453:36: error: 'vector' in namespace 'std' does not name a template type FEDAPVErrorHeader(const std::vector& apvsGood = std::vector(APVS_PER_FED,true)); ^~~~~~ /build/cmsbld/jenkins/workspace/ib-any-integration/CMSSW_10_6_X_2019-04-02-1100/src/EventFilter/SiStripRawToDigi/interface/SiStripFEDBufferComponents.h:453:42: error: expected ',' or '...' before '<' token FEDAPVErrorHeader(const std::vector& apvsGood = std::vector(APVS_PER_FED,true)); ^ |
Comparison not run due to Build errors (RelVals and Igprof tests were also skipped) |
please test |
The tests are being triggered in jenkins. |
+1 |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
+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. @davidlange6, @slava77, @smuzaffar, @fabiocos (and backports should be raised in the release meeting by the corresponding L2) |
@Dr15Jones @smuzaffar the reported compilation warning looks real, and I can easily it fix in a separate PR. But it looks to me that the fednum variable is unused regardless of this PR, so why is it popping out only now? The change introduced by this PR is that FEDNumbering has no more private data members. |
@fabiocos I promise to fix the new compilation warning in another pull request. No good guess as to why it only appears now. |
+1 |
PR description:
Removed the thread unsafe initialization of static member data. Change to initialize the data either at compile time (via the use of constexpr) or at shared library load time.
PR validation:
The code compiles and a new unit test was added to check the code.