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
Move PixelBarrelName and PixelEndcapName into TrackerCommon to avoid circular dependency #31380
Conversation
The code-checks are being triggered in jenkins. |
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-31380/18202
Code check has found code style and quality issues which could be resolved by applying following patch(s)
|
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-31380/18203
|
A new Pull Request was created by @davidlange6 (David Lange) for master. It involves the following packages: Alignment/TrackerAlignment @perrotta, @Martin-Grunewald, @andrius-k, @kmaeshima, @tocheng, @tlampen, @christopheralanwest, @civanch, @mdhildreth, @cmsbuild, @jpata, @jfernan2, @fioriNTU, @slava77, @ggovi, @fwyzard, @pohsun can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
The tests are being triggered in jenkins.
|
+1
|
+alca |
@VinInn please open a CMSSW issue, so it doesn't fall off the radar (given the rather low priority) |
I'll leave it to reco conveners (if they think is worth/relevant/correct) |
As far as I can tell, the packages involved https://github.com/cms-sw/cms-bot/blob/master/categories_map.py#L1425 https://github.com/cms-sw/cms-bot/blob/master/categories_map.py#L1428 |
+1 |
+1 |
+1 |
@cms-sw/db-l2 could you please have a look and sign, if you think so? It is just a quite technical PR, and since it involves several files, it is proabably worth trying to merge it now and avoid thus possible conflicts in future... |
+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 |
No description provided.