-
Notifications
You must be signed in to change notification settings - Fork 4.6k
fix handling of nano steps in Patatrack workflows #36309
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
|
type bug-fix |
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-36309/27047
|
|
A new Pull Request was created by @kpedro88 (Kevin Pedro) for master. It involves the following packages:
@jordan-martins, @bbilin, @wajidalikhan, @cmsbuild, @AdrianoDee, @srimanob, @kskovpen can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
|
test parameters: |
|
please test |
|
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-af1131/20896/summary.html Comparison Summary@slava77 comparisons for the following workflows were not done due to missing matrix map:
Summary:
|
|
Trying to understand what happened: the |
|
Yes, that's correct. |
|
+Upgrade Technical PR to fix the Patatrack workflow. |
|
@cms-sw/pdmv-l2 this fix should be included in pre3: could you please have a look and sign, if you think so? |
|
+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. @perrotta, @dpiparo, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
|
+1 |
|
@kpedro88 I see issues with nano wfs in the IB RelVals after this PR was merged: Can you please have a look? |
PR description:
This fixes an unexpected interaction between the existing Patatrack workflow setup and the new Run3 reco/harvest+nano combined steps (reported in #36167 (comment)).
PR validation:
Checked that missing steps reappeared in output of
runTheMatrix.py -w gpu -l 11634.506 --dryRun. This also affects 11634.505, which is a CPU workflow in the regular matrix, so it can be used for testing this PR more easily.