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
Consumes migration for triggerResultsByName #14262
Consumes migration for triggerResultsByName #14262
Conversation
A new Pull Request was created by @wddgit (W. David Dagenhart) for CMSSW_8_1_X. It involves the following packages: DataFormats/FWLite @cmsbuild, @smuzaffar, @Dr15Jones, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are list here #13028 |
please test |
The tests are being triggered in jenkins. |
if(resultsByNameHLT.isValid() && expectedTriggerResultsHLT_.size() > 0) { | ||
edm::InputTag tag("TriggerResults", "", "HLT"); | ||
edm::Handle<edm::TriggerResults> hTriggerResults; | ||
e.getByLabel(tag, hTriggerResults); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since this is Core code, how about changing to getByToken
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This a module used only for tests. It has both a call to getManyByType and also getByLabel, both getting the TriggerResults type. There is a consumesMany call that allows both of those to work. I am not sure what happens if you call both consumes to get a token and also consumesMany for the same type.
+1 |
@smuzaffar - it seems that the error harvesting didn't work above... |
@smuzaffar Looking at the unit test log I found
Very strange that cppunit said there was an error but the test framework thought there was not. |
I think I found the reason scram thinks everything is OK. The test writer didn't use the standard way of running the tests: that specially made |
@davidlange6 , it could be that unit tests took more than 7200s to finish. |
Note that SUSYBSMAnalysis/HSCP/plugins/HSCPValidator.cc shows many lines changed only because the previous version had DOS line endings. Ignoring that, the changes in that file are almost the same as in SUSYBSMAnalysis/HSCP/plugins/HSCPHLTFilter.cc.