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
ME0MuonSelector cleanup pass #31190
ME0MuonSelector cleanup pass #31190
Conversation
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-31190/17828
|
A new Pull Request was created by @davidlange6 (David Lange) for master. It involves the following packages: CommonTools/RecoAlgos @perrotta, @jpata, @cmsbuild, @slava77 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
The tests are being triggered in jenkins. |
Hi @davidlange6, I have to mention something else related to this It is used in Therefore, we have a rather awkward dependency relation between be packages: Would you also think it's better to have everything in In practice, this suggestion implies to move: |
By the way, something else that could be cleaned straightforwardly in this ME0MuonTrackCollProducer.cc is the following (just listing what jumps to the eyes as being obviously uselessly included):
as well as the commented out line
|
@Fedespring @cericeci : profiting of this PR, could you plese check if all those "ME0" muons stuffs are still needed at all in the standard workflows (or any other "local" one)? If not, this could be a good opportunity to start cleaning all them out |
Clearly that would be an improvement, yes. [but I don't really follow the design logic (or why we would need a ME0 specific muon selector)] Probably best addressed by those responsible for muon selectors? |
please test |
The tests are being triggered in jenkins.
|
-1 Tested at: b6acc69 CMSSW: CMSSW_11_2_X_2020-08-23-2300 I found follow errors while testing this PR Failed tests: Build
I found compilation error when building: >> Compiling edm plugin /data/cmsbld/jenkins/workspace/ib-run-pr-tests/CMSSW_11_2_X_2020-08-23-2300/src/CommonTools/RecoAlgos/plugins/VertexRefSelector.cc >> Compiling edm plugin /data/cmsbld/jenkins/workspace/ib-run-pr-tests/CMSSW_11_2_X_2020-08-23-2300/src/CommonTools/RecoAlgos/plugins/VertexSelector.cc >> Building edm plugin tmp/slc7_amd64_gcc820/src/CommonTools/RecoAlgos/plugins/CommonToolsRecoAlgos_plugins/libCommonToolsRecoAlgos_plugins.so /cvmfs/cms-ib.cern.ch/nweek-02643/slc7_amd64_gcc820/external/gcc/8.2.0-bcolbf/bin/../lib/gcc/x86_64-unknown-linux-gnu/8.4.0/../../../../x86_64-unknown-linux-gnu/bin/ld: tmp/slc7_amd64_gcc820/src/CommonTools/RecoAlgos/plugins/CommonToolsRecoAlgos_plugins/ME0MuonTrackCollProducer.cc.o: in function `ME0MuonTrackCollProducer::produce(edm::Event&, edm::EventSetup const&)': ME0MuonTrackCollProducer.cc:(.text+0x512): undefined reference to `muon::me0::isGoodMuon(reco::ME0Muon const&, muon::me0::SelectionType)' collect2: error: ld returned 1 exit status gmake: *** [tmp/slc7_amd64_gcc820/src/CommonTools/RecoAlgos/plugins/CommonToolsRecoAlgos_plugins/libCommonToolsRecoAlgos_plugins.so] Error 1 Leaving library rule at src/CommonTools/RecoAlgos/plugins Entering library rule at CommonTools/RecoAlgos >> Compiling /data/cmsbld/jenkins/workspace/ib-run-pr-tests/CMSSW_11_2_X_2020-08-23-2300/src/CommonTools/RecoAlgos/src/ClusterStorer.cc >> Compiling /data/cmsbld/jenkins/workspace/ib-run-pr-tests/CMSSW_11_2_X_2020-08-23-2300/src/CommonTools/RecoAlgos/src/MassiveCandidateConverter.cc |
Comparison not run due to Build errors (RelVals and Igprof tests were also skipped) |
Odd, I had to reload to see the word “fatal” in that log.. ok, I will restart the tests..
On Aug 24, 2020, at 5:52 PM, Matti Kortelainen <notifications@github.com<mailto:notifications@github.com>> wrote:
Hmm, I see at the end of
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-6a2320/8878/addOnTests/hlt_data_GRun/cmsDriver.py_RelVal_-s_L1REPACK:Full_--data_--scenario=pp_-n_10_--conditions_auto:run3_hlt_GRun_--relval_9000,50_--datatier_RAW_--eventcontent_RAW_-.log
only
Fatal system signal has occurred during exit
We've seen that symptom before on cc8 that lead to #30432<#30432>.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#31190 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABGPFQ5VWP5R76B2TF4NFB3SCKEEPANCNFSM4QFXM3EA>.
|
please test
|
The tests are being triggered in jenkins.
|
+1 |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
I don't think this simple PR should be delayed any further, |
+1
|
This pull request is fully signed and it will be integrated in one of the next master IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @silviodonato, @dpiparo, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
The modules IB pointed out duplicated structs between MuonSelector and ME0MuonSelector. To avoid this, I added a namespace to the me0 set of functions for lack of better idea.
There were in addition #includes of plugin/*.cc files which have been cleaned up and rearranged to avoid duplicate plugin problems. There may be other issues not fixed by this PR.. [Perhaps #including cc files can be prevented by code checks...:)