-
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
JPT_TrackJetsSeeds_Reco_and_PATrereco #30160
Conversation
…tHLT_29333 [11.1.X] Applied gain calibration scheme update at HLT as well
Run3-ft25 Fix overlap for run3 geometry - backport cms-sw#29953
…date111X HLT customisation update (111X)
[11.1.X] Fix several bugs introduced in the Pixel PI
…oducerIn11 Fixes in PSetBlobProducer functionality for use in HLT (11_1_X)
Fix DetectorDescription Parser unit test -- backport of cms-sw#29947
…_deadECAL Restructured code of againstElectronDeadECAL tauID (11_1_X)
…pre8for111X Migration of HLT menus to 11_1_0_pre8 template plus updates (11_1_X)
Davix unit test fix: use google instead of cern.ch
…onst_on_return Do not apply the "const" modifier to the return type (11.1.x)
[11.1.X] Add CDC Tracks to TkAlCosmics0T ALCARECO
…et-pre5 Backport of PR cms-sw#29527 (L1 tracking)
…_TauIdToolFix bug fix to runTauIdMVA.py tool (11_1_X)
…dFix Fix bug affecting boosted tau isolation (11_1_X)
…eTags_11_1_X 11.1.X [Tracker Alignment] All-in-one tool support of multiple tags in user-inputed sqlite file
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-30160/15991
|
A new Pull Request was created by @kodolova (kodolova) for master. It involves the following packages: Alignment/CommonAlignmentProducer @andrius-k, @emeschi, @schneiml, @ianna, @kpedro88, @Martin-Grunewald, @rekovic, @fioriNTU, @tlampen, @pohsun, @santocch, @perrotta, @civanch, @makortel, @cmsbuild, @fwyzard, @davidlange6, @smuzaffar, @Dr15Jones, @cvuosalo, @mdhildreth, @jfernan2, @tocheng, @slava77, @ggovi, @fabiocos, @benkrikler, @kmaeshima, @christopheralanwest, @silviodonato, @franzoni, @mommsen can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
-1 |
Dear All, I ran code over patch as it was proposed, made add, commit push. But I am sorry, could you advice how to rebase and how to change the name of PR as Slava requested? |
There is an "Edit" button at the top of the page, to the right from the PR title |
did you try http://cms-sw.github.io/tutorial-resolve-conflicts.html |
Slava, I did code-format with patch. I looked into http://cms-sw.github.io/tutorial-resolve-conflicts.html but I do not understand what exact command I need to perform: |
code made in 11_1_X can not be directly made as a PR to 11_2_X (master branch) as it is done here.
the new release would be one of the CMSSW_11_2_X IBs |
Done. Thank you! |
was it pushed as well? |
No, I thought that it is done automatically. I am sorry but there is not good instruction step by step how to work with git. |
Dear Olga, I followed line by line the instructions posted above by Slava and I ended up with a github branch in 11_2_X which only contains your commits:
At this point you can simply try to push in your current branch
or, if it fails for any reason, just open a new branch and submit a new PR with it (and close this one), as I could have done with
for which you can check my perrotta:jptFromKodolova branch. |
Thank you! I repeated in new project area and got the same error. I think that I do need to open the new branch and new PR. Something is broken with this one. |
I have created the new PULL request. How to kill #30160? |
Sorry again... When I try: https://github.com/kodolova/cmssw |
Please stay in THIS pull request |
-1 |
PR description:
Presented at Reconstruction meeting
https://indico.cern.ch/event/923095/
PR validation:
Tests are performed according:https://cms-sw.github.io/PRWorkflow.html
Result of runTheMatrix test is in:
/afs/cern.ch/work/k/kodolova/public/HMUMUBB/CMSSW_11_1_X_2020-06-08-1100/src
if this PR is a backport please specify the original PR and why you need to backport that PR:
Before submitting your pull requests, make sure you followed this checklist: