-
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
[14_0_X] DQM: temporary fix of the crash of hlt DQM client using TryToContinue #44652
Conversation
A new Pull Request was created by @syuvivida for CMSSW_14_0_X. It involves the following packages:
@cmsbuild, @rvenditti, @syuvivida, @tjavaid, @nothingface0, @antoniovagnerini can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
cms-bot internal usage |
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-98fa28/38672/summary.html Comparison SummarySummary:
|
Pull request #44652 was updated. @cmsbuild, @nothingface0, @antoniovagnerini, @rvenditti, @tjavaid, @syuvivida can you please check and sign again. |
Pull request #44652 was updated. @tjavaid, @antoniovagnerini, @syuvivida, @rvenditti, @nothingface0, @cmsbuild can you please check and sign again. |
Hi sorry, I was making commit of another code unrelated to HLT clients. I will close this PR first (since it is not clear if we need to add this protection) |
PR description:
Starting from the first run with 13.6 TeV collisions and stable beam run378981, we see crashes from the client
hlt_dqm_sourceclient-live_cfg.py. More details are discussed in this github issue. While the CMSSW core team, HLT, and DQM are investigating the issues, we added a temporary fix using "TryToContinue" when a product is not found.
PR validation:
This PR was tested at p5 playback machines using the streamers containing the LSs of run 378981 in which this hlt client crashed. Additionally this PR has been deployed in online production machine starting from run 379059. No more crashes were observed. But given that the root cause was not yet resolved, one could see warning messages as