-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Remove Passthrough Pattern Recognition from TICLv4 #45272
Remove Passthrough Pattern Recognition from TICLv4 #45272
Conversation
cms-bot internal usage |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-45272/40660
|
A new Pull Request was created by @waredjeb for master. It involves the following packages:
@cmsbuild, @srimanob, @jfernan2, @mandrenguyen, @subirsarkar can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test workflow 29696.203, 29896.203 |
Hi @mandrenguyen thanks for the tests! These two workflows are for Phase-2, don't we need the options |
@cmsbuild please abort |
test parameters:
|
@cmsbuild please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-4e2229/39997/summary.html
Comparison SummarySummary:
|
+1 |
So, I am not sure what happended, DAS says that workflows *203 have failed, and I don't see the comparison with the baseline. But looking at the runMatrix output looks like the workflows ran correctly: |
+Upgrade |
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. @antoniovilela, @sextonkennedy, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
Hi! @antoniovilela it would be nice if this could be merged before pre5 is built! |
+1 |
This PR removes the PassThrough pattern recognition (developed for TICLv5) that was incorrectly introduced in TICLv4.
No changes are expected in physics since the additional collection was not used anywhere else in the TICL workflow.
Should be tested with any *.203 workflow (e.g. 29696.203 and 29896.203 )