Skip to content
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

IB issues: TPTask::Collection HcalTrigPrimDigiCollection isn't available: valHcalTriggerPrimitiveDigis #36188

Closed
qliphy opened this issue Nov 20, 2021 · 8 comments

Comments

@qliphy
Copy link
Contributor

qliphy commented Nov 20, 2021

Appearing in many workflows 136.XXX

https://cmssdt.cern.ch/SDT/cgi-bin/logreader/slc7_amd64_gcc900/CMSSW_12_2_X_2021-11-19-2300/pyRelValMatrixLogs/run/136.761_RunJetHT2016E+RunJetHT2016E+HLTDR2_2016+RECODR2_2016reHLT_skimJetHT_HIPM+HARVESTDR2_skimJetHT/step3_RunJetHT2016E+RunJetHT2016E+HLTDR2_2016+RECODR2_2016reHLT_skimJetHT_HIPM+HARVESTDR2_skimJetHT.log#/120-120

An exception of category 'HCALDQM' occurred while
[0] Processing Event run: 277069 lumi: 91 event: 54448390 stream: 3
[1] Running path 'dqmoffline_1_step'
[2] Calling method for module TPTask/'tpTask'
Exception Message:
TPTask::Collection HcalTrigPrimDigiCollection isn't available: valHcalTriggerPrimitiveDigis

@cmsbuild
Copy link
Contributor

A new Issue was created by @qliphy Qiang Li.

@Dr15Jones, @perrotta, @dpiparo, @makortel, @smuzaffar, @qliphy can you please review it and eventually sign/assign? Thanks.

cms-bot commands are listed here

@qliphy
Copy link
Contributor Author

qliphy commented Nov 20, 2021

Related to #35678

@kskovpen

@qliphy
Copy link
Contributor Author

qliphy commented Nov 20, 2021

assign dqm

@cmsbuild
Copy link
Contributor

New categories assigned: dqm

@jfernan2,@ahmad3213,@rvenditti,@emanueleusai,@pbo0,@pmandrik you have been requested to review this Pull request/Issue and eventually sign? Thanks

@perrotta
Copy link
Contributor

Quite likely related: a few of those 136.XXX workflows (e.g. 136.829, 136.886, 136.8861, 136.8862) now fail in step4 with a segmentation violation. Before that, the step4 logs are flooded with messages like

%MSG-w DTMonitorModule:   DTResolutionAnalysisTest:dtResolutionAnalysisTest@endProcessBlock  20-Nov-2021 03:10:10 CET post-events
[DTResolutionAnalysisTask] Histo: DT/02-Segments/Wheel-2/Sector3/Station1/hResDist_W-2_St1_Sec3_SL1 not found

This is also specific of the latest CMSSW_12_2 2021-11-19-2300 IB

@perrotta
Copy link
Contributor

By looking at its log outputs I can notice that #36194 fixes both the exceptions/segm_violations and the flooding of messages from the DTMonitorModule that were reported above

@jfernan2
Copy link
Contributor

+1

@cmsbuild
Copy link
Contributor

This issue is fully signed and ready to be closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants