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
[10.1.X] fix segmentation fault in SiStripBadComponentInfo (backport) #22818
[10.1.X] fix segmentation fault in SiStripBadComponentInfo (backport) #22818
Conversation
…fix of the new crashing module" This reverts commit 77374d2.
A new Pull Request was created by @mmusich (Marco Musich) for CMSSW_10_1_X. It involves the following packages: DQM/SiStripMonitorClient @vazzolini, @kmaeshima, @dmitrijus, @cmsbuild, @jfernan2, @vanbesien can you please review it and eventually sign? Thanks. cms-bot commands are listed here
|
please test |
The tests are being triggered in jenkins. |
please test |
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 CMSSW_10_1_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_10_2_X is complete. 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) |
+1 |
backport of #22719
Title says is it all: attempt to fix issue #22695.
Access to the
TrackerTopology
from DB is moved fromdqmEndJob
toendRun
where framework should guaranteeedm::EventSetup
components are still accessible. Bin contents of the output monitor element are cached in astd::map
.This reverts also #22690.
Tested locally with wf.
runTheMatrix.py -l 4.6 -t 4
type bug-fix