-
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
Bug fix pat::TriggerObjectStandAlone #19942
Bug fix pat::TriggerObjectStandAlone #19942
Conversation
In order to interact with a TriggerObjectStandAlone one needs a non-const instance. The copy function makes it easier to get a non-const from a const.
The previous code was calling the product registry directly and assumed calling EventBase::triggerNames would always update the registry. That assumption was incorrect. The registry was only updated if the triggerNames PSet was not found in the cache. Calling EventBase::parameterSet does guarantee that the registry is up to date.
A new Pull Request was created by @Dr15Jones (Chris Jones) for master. It involves the following packages: DataFormats/PatCandidates @perrotta, @cmsbuild, @slava77, @monttj, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
The tests are being triggered in jenkins. |
This fixes the problem reported here: |
-1 Tested at: 217e542 The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic: You can see the results of the tests here: I found follow errors while testing this PR Failed tests: UnitTests
I found errors in the following unit tests: The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic: |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
The error in the unit test is unrelated: stat: cannot stat `dqm_empty.root': No such file or directory |
please test |
The tests are being triggered in jenkins. |
-1 Tested at: 217e542 The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic: You can see the results of the tests here: I found follow errors while testing this PR Failed tests: RelVals AddOn
When I ran the RelVals I found an error in the following worklfows: runTheMatrix-results/10042.0_ZMM_13+ZMM_13TeV_TuneCUETP8M1_2017_GenSimFull+DigiFull_2017+RecoFull_2017+ALCAFull_2017+HARVESTFull_2017/step2_ZMM_13+ZMM_13TeV_TuneCUETP8M1_2017_GenSimFull+DigiFull_2017+RecoFull_2017+ALCAFull_2017+HARVESTFull_2017.log10024.0 step2 runTheMatrix-results/10024.0_TTbar_13+TTbar_13TeV_TuneCUETP8M1_2017_GenSimFull+DigiFull_2017+RecoFull_2017+ALCAFull_2017+HARVESTFull_2017/step2_TTbar_13+TTbar_13TeV_TuneCUETP8M1_2017_GenSimFull+DigiFull_2017+RecoFull_2017+ALCAFull_2017+HARVESTFull_2017.log10824.0 step2 runTheMatrix-results/10824.0_TTbar_13+TTbar_13TeV_TuneCUETP8M1_2018_GenSimFull+DigiFull_2018+RecoFull_2018+ALCAFull_2018+HARVESTFull_2018/step2_TTbar_13+TTbar_13TeV_TuneCUETP8M1_2018_GenSimFull+DigiFull_2018+RecoFull_2018+ALCAFull_2018+HARVESTFull_2018.log
I found errors in the following addon tests: cmsRun /cvmfs/cms-ib.cern.ch/nweek-02482/slc6_amd64_gcc630/cms/cmssw-patch/CMSSW_9_3_X_2017-07-28-1100/src/HLTrigger/Configuration/test/OnLine_HLT_2e34_v2.py realData=False globalTag=@ inputFiles=@ : FAILED - time: date Fri Jul 28 17:57:52 2017-date Fri Jul 28 17:36:48 2017 s - exit: 21248 The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic: |
Comparison not run due to runTheMatrix errors (RelVals and Igprof tests were also skipped) |
The failures of the tests are unrelated to this pull request (i.e. they are already present in the IB). |
please test |
The tests are being triggered in jenkins. |
+1 The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic: |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
merge |
The pat::TriggerObjectStandAlone was directly calling the ParameterSet registry assuming that a
previous call would fill the registry. That assumption was incorrect. Now the class calls the method
EventBase::parameterSet which will do the necessary up dating of the registry behind the scenes.