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
Unit Failure in 12_X IB from TauAnalysis/MCEmbeddingTools #34112
Comments
A new Issue was created by @qliphy Qiang Li. @Dr15Jones, @dpiparo, @silviodonato, @smuzaffar, @makortel, @qliphy can you please review it and eventually sign/assign? Thanks. cms-bot commands are listed here |
@smuzaffar |
hm, if this test was running so far - how it worked in first place and if it did - how this file was read from this private eos area |
@mrodozov I think that's done with the usual trick of changing the eos address at the level of DAS query.
|
@mmusich @mrodozov, thank you. By reading the config files produced during the test, I believe I have found the issue: since the MERGE_PAT.py file is created with The solution is to add the associations to the collections to be removed in https://github.com/cms-sw/cmssw/blob/master/PhysicsTools/PatAlgos/python/tools/coreTools.py. |
Since CMSSW_12_0_X_2021-06-13-2300, we have a unit failure from TauAnalysis/MCEmbeddingTools
https://cmssdt.cern.ch/SDT/cgi-bin/logreader/slc7_amd64_gcc900/CMSSW_12_0_X_2021-06-13-2300/unitTestLogs/TauAnalysis/MCEmbeddingTools#/654-654
----- Begin Fatal Exception 14-Jun-2021 01:13:37 CEST-----------------------
An exception of category 'ProductNotFound' occurred while
[0] Processing Event run: 274199 lumi: 125 event: 245779397 stream: 0
[1] Running path 'MINIAODSIMoutput_step'
[2] Prefetching for module PoolOutputModule/'MINIAODSIMoutput'
[3] Calling method for module PackedCandidateGenAssociationProducer/'lostTracksToGenAssociation'
Exception Message:
Principal::getByToken: Found zero products matching all criteria
Looking for type: edm::Association<std::vectorreco::GenParticle >
Looking for module label: prunedGenParticles
Looking for productInstanceName:
Additional Info:
[a] If you wish to continue processing events after a ProductNotFound exception,
add "SkipEvent = cms.untracked.vstring('ProductNotFound')" to the "options" PSet in the configuration.
The text was updated successfully, but these errors were encountered: