-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Global CaloL1 DQM Fix #32205
Global CaloL1 DQM Fix #32205
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-32205/19948
|
A new Pull Request was created by @aloeliger for master. It involves the following packages: DQM/L1TMonitor @andrius-k, @kmaeshima, @ErnestaP, @cmsbuild, @jfernan2, @fioriNTU 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 |
Comparison job queued. |
Comparison is ready @slava77 comparisons for the following workflows were not done due to missing matrix map:
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. @silviodonato, @dpiparo, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
@aloeliger the L1TStage2CaloLayer1 class is producing a crash at Online in view of the next MWGR: Fatal Exception (Exit Code: 8022)An exception of category 'FatalRootError' occurred while The issue seems to be located on: |
PR description:
This PR adds fixes on top of the reverted CaloL1 DQM "Global" module change #32004, fixing issue #32172. The segmentation violation was caused by a bad binary search in a list of recent mismatches (caused by 2 issues: a wrongly shifted search location, and failure to exclude the previous search location from new search bounds) which caused a stack overflow.
PR validation:
The code compiles, and has been tested for online and single threaded offline use was tested in previous PR #32004. In addition, this change has now been tested on offline workflows 136.721 and 136.731 using 4 threads successfully.
if this PR is a backport please specify the original PR and why you need to backport that PR:
This PR is not a backport.