-
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
esConsumes migration for EDModules in SiStrip packages, part 1 #31826
esConsumes migration for EDModules in SiStrip packages, part 1 #31826
Conversation
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-31826/19126
|
A new Pull Request was created by @pieterdavid (Pieter David) for master. It involves the following packages: AnalysisAlgos/SiStripClusterInfoProducer @perrotta, @andrius-k, @yuanchao, @kmaeshima, @emeschi, @tlampen, @christopheralanwest, @ErnestaP, @tocheng, @cmsbuild, @jpata, @jfernan2, @fioriNTU, @slava77, @ggovi, @pohsun, @santocch, @smorovic 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 |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
@pieterdavid it seems this PR creates a huge number of changes in MEs located at AlCaReco and SiStrip folder for several workflows, |
+1 |
+1 |
+1
|
@ggovi @cms-sw/db-l2 do you have any comments? |
+1 |
@cms-sw/daq-l2 ? |
+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 |
PR description:
esConsumes migration #31061 for modules in packages with SiStrip in the name, outside
DQM/
(which more or less splits the list in two - the rest will be submitted as a separate PR).I tried to follow the instructions from #31061, and keep other changes minimal.
I rebased on an IB after #31756 was merged and did not change the modules migrated in #31697 (SimTracker/SiStripDigitizer and SiStripFedZeroSuppression), so in principle there should be no conflicts.
PR validation:
compiles, and
runTheMatrix.py -l limited --useInput all
passes - I'm not sure that checks all the transitions/updates, hints on validating that are welcome.