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
standardize implementation and offsets for special tracking workflows #21932
Conversation
The code-checks are being triggered in jenkins. |
@makortel please take a look |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-21932/3000 |
A new Pull Request was created by @kpedro88 (Kevin Pedro) for master. It involves the following packages: Configuration/PyReleaseValidation @cmsbuild, @GurpreetSinghChahal, @prebello, @kpedro88, @fabozzi can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
The tests are being triggered in jenkins. |
please abort |
1 similar comment
please abort |
Jenkins tests are aborted. |
cb8ec60
to
d679980
Compare
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-21932/3001 |
please test |
The tests are being triggered in jenkins. |
Comparison job queued. |
Comparison is ready @slava77 comparisons for the following workflows were not done due to missing matrix map:
Comparison Summary:
|
@makortel ping |
+1 |
@kpedro88 Sorry for the delay. Looks good to me (as far as I could understand by just reading). Thanks for the generalization. |
+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. @davidlange6, @slava77, @smuzaffar, @fabiocos (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
In #18503 I tried to standardize the implementation of "special" workflows, but only propagated this to Phase2, ignoring Phase1.
This led to some offset numbers being used inconsistently between Phase1 and Phase2, as well as novel code in relval_2017 (which I would prefer to keep as a strict forwarding file to pass workflow numbers between the upgrade matrix and regular matrix).
I've moved all the special tracking workflows from relval_2017 into the new approach (all definitions/conditions in
upgradeWorkflowComponents
,relval_steps
, andrelval_upgrade
). I checked thecmsDriver
commands before and after the change usingrunTheMatrix.py --dryRun
to make sure nothing was unintentionally altered.In the process, I fixed a bug that the 2018 tracking workflows were actually using 2017 steps. I also changed the offset numbers for the Phase 2 timing and neutron workflows to be separate from the tracking workflows.