-
Notifications
You must be signed in to change notification settings - Fork 4.4k
Fix siPixelDigiMorphing
modifer and create workflows to test it
#47872
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
Conversation
cms-bot internal usage |
RecoLocalTracker/SiPixelClusterizer/python/SiPixelClusterizerPreSplitting_cfi.py
Show resolved
Hide resolved
Configuration/PyReleaseValidation/python/upgradeWorkflowComponents.py
Outdated
Show resolved
Hide resolved
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-47872/44519
|
A new Pull Request was created by @mmusich for master. It involves the following packages:
@AdrianoDee, @Moanwar, @cmsbuild, @DickyChant, @jfernan2, @mandrenguyen, @miquork, @srimanob, @subirsarkar can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
8352621
to
520f256
Compare
test parameters:
|
waiting for #47881 to be resolved before launching tests. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-47872/44521
|
Pull request #47872 was updated. @AdrianoDee, @Moanwar, @cmsbuild, @DickyChant, @jfernan2, @mandrenguyen, @miquork, @srimanob, @subirsarkar can you please check and sign again. |
+1 Size: This PR adds an extra 40KB to repository Comparison SummarySummary:
|
+1 |
+Upgrade |
+pdmv |
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. @rappoccio, @antoniovilela, @sextonkennedy, @mandrenguyen (and backports should be raised in the release meeting by the corresponding L2) |
type bugfix |
+1 |
PR description:
Title says it all.
PR validation:
Run
runTheMatrix.py -l 16834.18
If this PR is a backport please specify the original PR and why you need to backport that PR. If this PR will be backported please specify to which release cycle the backport is meant for:
Not a backport, might be backported