Skip to content
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

Pcc_event_producer_11_1_x_2020_02_18_1100 #28992

Conversation

samhiggie
Copy link
Contributor

PR description:
Continuation of PR #28807 #28807
and rebase of PR #28980 #28980 - will close after verification

Changed some of the names of the producers to match the nomenclature by most modules in cmssw.

Added a fillDescription method so that the new AlCaPCCEventProducer may be added to the HLT configuration

Removed a PSet formatting

PR validation:
Compiles and Runs with local test files and HLT configuration like:
hltGetConfiguration /users/sharper/2019/alca/alcaLumi --setup /dev/CMSSW_10_6_0/GRun/V3 --globaltag auto:run2_hlt_GRun --unprescale > hlt.py
(must replace AlcaPCCProducer with AlcaPCCEventProducer)
FastReport Info:

FastReport CPU time sched. / depend. Real time sched. / depend. Alloc. sched. / depend. Dealloc. sched. / depend. Processes and Paths
FastReport 3.4 ms 3.4 ms 6.3 ms 6.3 ms +3333 kB +3333 kB -3081 kB -3081 kB Alca_LumiPixelsCounts_ZeroBias_v1
FastReport 0.0 ms 0.0 ms 0.1 ms 0.1 ms +0 kB +0 kB +0 kB +0 kB Alca_LumiPixelsCounts_Random_v1

@cmsbuild cmsbuild changed the base branch from CMSSW_11_1_X to master February 18, 2020 23:22
@cmsbuild
Copy link
Contributor

@samhiggie, CMSSW_11_1_X branch is closed for direct updates. cms-bot is going to move this PR to master branch.
In future, please use cmssw master branch to submit your changes.

@cmsbuild
Copy link
Contributor

The code-checks are being triggered in jenkins.

@cmsbuild
Copy link
Contributor

-code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-28992/13827

Code check has found code style and quality issues which could be resolved by applying following patch(s)

@slava77
Copy link
Contributor

slava77 commented Feb 19, 2020

-1

due to merge conflicts

@samhiggie
Copy link
Contributor Author

samhiggie commented Feb 20, 2020

Greetings @slava77 , can you please be more specific?
I needed to update the classes_def.xml for a successful build.
For the AlcaPCCProducerEvent: I changed the naming scheme to match what current producers are called "XXXProducer" so I named it AlcaPCCEventProducer. In addition, I removed a useless cms Parameter Set from the module.
I'm happy to address other issues.

@slava77
Copy link
Contributor

slava77 commented Feb 20, 2020

Greetings @slava77 , can you please be more specific?

I mean the status of this PR is unmergeable, as can be seen at the bottom of the page, screen-shot is below

Screen Shot 2020-02-20 at 4 44 19 AM

http://cms-sw.github.io/tutorial-resolve-conflicts.html or even a web search for "git resolve merge conflicts" can help

@silviodonato
Copy link
Contributor

Please open a new PR using a branch based on a more recent release

@samhiggie
Copy link
Contributor Author

samhiggie commented Feb 26, 2020

Greetings @silviodonato, I just created a branch on a more recent release(from 11_1_X to 11_1_X_2020_02_18_1100 ) at your request #28980 (comment).
If this isn't the right version, can you please tell me which version I should make the PR to?

@samhiggie
Copy link
Contributor Author

Hello, @silviodonato and @slava77. Do I need to rebase? or try a new release? or is this fine?

I haven't done a rebase in a while. If I need to do so, could you provide the branch you'd like me to rebase to?

As mentioned previously, the merge conflicts are producer names and class versions in the buildfile.xml. Every works locally just fine. Please let me know how this can be resolved. Thank you.

@slava77
Copy link
Contributor

slava77 commented Feb 27, 2020

Based on https://github.com/cms-sw/cmssw/compare/master...samhiggie:PCCEventProducer_11_1_X_2020-02-18-1100?expand=1, you can see that this is still not mergeable.

rebase instructions are available in http://cms-sw.github.io/tutorial-resolve-conflicts.html
(you may even try to skip to "I need a quick recipe" if the intro material seems too long)

@samhiggie
Copy link
Contributor Author

Hello @slava77 , I've successfully rebased on #29069

This was frustrating though, as all the commits that I had posted I needed to go through and many contained changes that were not necessary or I changed in order to forget them. In the future, is there a way I can just drop commits that are useless so I don't need to go through each one?
OR if the state of the branch is in good condition is it possible to just sign off on the conflicts?

Cheers,
Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants