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
SiStripMonitorClient: Fix caching logic in SiStripBadComponentInfo #24955
SiStripMonitorClient: Fix caching logic in SiStripBadComponentInfo #24955
Conversation
... by removing it. Also avoid a needless copy.
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-24955/6927 |
@schneiml we shall see it in the relval comparisons (as this module is tested there). |
please test |
The tests are being triggered in jenkins. |
A new Pull Request was created by @schneiml (Marcel Schneider) for master. It involves the following packages: DQM/SiStripMonitorClient @kmaeshima, @cmsbuild, @andrius-k, @jfernan2, @schneiml can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
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) |
+1 |
... by removing it. Also avoid a needless copy.
Thanks to @Dr15Jones and @makortel in #24924 for pointing out that this logic seems to be quite broken.
@mmusich this seems to fix the crash with multi-run harvesting, but it is hard to validate for me if the basic behavior changed. But, the change seems safe from the technical side.
Required for #24920, but independent.