-
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
Fatal Exception in Express processing with CMSSW_13_0_7 #41843
Comments
A new Issue was created by @francescobrivio . @Dr15Jones, @perrotta, @dpiparo, @rappoccio, @makortel, @smuzaffar can you please review it and eventually sign/assign? Thanks. cms-bot commands are listed here |
assign reconstruction,btv-pog |
New categories assigned: btv-pog,reconstruction @mandrenguyen,@clacaputo,@soureek,@johnalison you have been requested to review this Pull request/Issue and eventually sign? Thanks |
A possible PR which entered in 13_0_7 and touched PNet DQM is #41704 |
assign dqm |
New categories assigned: dqm @tjavaid,@micsucmed,@nothingface0,@rvenditti,@emanueleusai,@syuvivida,@pmandrik you have been requested to review this Pull request/Issue and eventually sign? Thanks |
urgent
|
let me tag also explicitly the people involved in this: @marinakolosova @rgerosa @scooperstein |
New categories assigned: hlt @missirol,@Martin-Grunewald you have been requested to review this Pull request/Issue and eventually sign? Thanks |
The exception gets thrown from
The dereferenced The module
(among others) |
It might be a misconfiguration of the eventContent of the |
|
I think the EventContent of the HLTMonitor stream was incorrect, and has been fixed in CMSHLT-2825. I think we have seen it only after deploying That said, I haven't verified that this fix (which is correct anyway) will solve this issue. If it does, the problem should not occur anymore starting from run-368321. |
Indeed starting from run |
Ok I haven't seen any other failure of this kind after run Before closing this issue, is there something we could do to:
|
In principle adding something along the following if (not jetPNETScoreHLTHandle->keyProduct().isAvailable()) {
edm::LogWarning("ParticleNetJetTagMonitor") << "Collection used as a key by HLT Jet tags collection is not available, will skip event";
return;
} before the loop
would the appropriate check for the availability of the key collection. Unfortunately that code does not work today, because edm::RefToBaseProd (the type returned by keyProduct() above) does not have isAvailable() member function. It looks to be straightforward to add though (and therefore will do).
|
The framework provides a TestProcessor facility that enables fairly easy testing of modules in isolation e.g. for various corner cases such as "Run had no lumis", "Lumi had no events", "Event does not contain the necessary data products". It is documented in https://github.com/cms-sw/cmssw/blob/master/FWCore/TestProcessor/Readme.md, and many examples can be found with "git grep TestProcessor". A notable example is in the skeleton templates https://github.com/cms-sw/cmssw/blob/master/FWCore/Skeletons/mkTemplates/EDProducer/test_catch2_EDProducer.cc |
The |
given the thread in #41858 (comment) it's not clear to me if the recommendation is to NOT protect the DQM code with this because of disk reading costs, or not. |
The DQM code de-references the corresponding cmssw/DQMOffline/Trigger/plugins/ParticleNetJetTagMonitor.cc Lines 871 to 872 in d2f6636
so the data would be read from storage in any case. So the cost of an isAvailable() check there should be negligible.
|
+hlt The EventContent of the HLTMonitor stream was fixed in CMSHLT-2825. |
There are some reported crashed in the Express processing of
StreamHLTMonitor
for run368318
(see CMSTalk post).The exception is:
Recipe to reproduce the error:
edit the
PSet.py
to be:run it with:
The text was updated successfully, but these errors were encountered: