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
Prevent possible segm violation in TopSingleLeptonHLTOfflineDQM #2401
Prevent possible segm violation in TopSingleLeptonHLTOfflineDQM #2401
Conversation
A new Pull Request was created by @perrotta for CMSSW_7_1_X. Prevent possible segm violation in TopSingleLeptonHLTOfflineDQM It involves the following packages: DQMOffline/Trigger @ojeda, @danduggan, @rovere, @cmsbuild, @nclopezo, @deguio, @Degano can you please review it and eventually sign? Thanks. |
-1 runTheMatrix-results/1001.0_RunMinBias2011A+RunMinBias2011A+TIER0EXP+ALCAEXP+ALCAHARVD/step2_RunMinBias2011A+RunMinBias2011A+TIER0EXP+ALCAEXP+ALCAHARVD.log you can see the results of the tests here: |
It looks like having nothing to do with the content of the pull request: filesFromList A. cmsbuild notifications@github.com ha scritto:
This message was sent using IMP, the Internet Messaging Program. |
+1 |
DQMOffline/Trigger -- Prevent possible segm violation in TopSingleLeptonHLTOfflineDQM
Oracle environment removal and Oracle related packages update
Prevent possible segm violation in DQMOffline.Trigger.TopSingleLeptonHLTOfflineDQM
The code is quite convoluted, and certainlly something better can be done.
However, by just allowing for jets the same kind of check on the vector boundary as it is done a few lines above for electrons and muons one can prevent a segmentation violation when the jet selector remove all jets from the vector correctedJets