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
[10_6 backport] Define proper BS for 2018 premixing workflow if starting from scratch #29402
[10_6 backport] Define proper BS for 2018 premixing workflow if starting from scratch #29402
Conversation
A new Pull Request was created by @srimanob (Phat Srimanobhas) for CMSSW_10_6_X. It involves the following packages: Configuration/PyReleaseValidation @chayanit, @cmsbuild, @wajidalikhan, @pgunnell, @kpedro88 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
backport of #29401 |
The tests are being triggered in jenkins. |
+1 |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
+1 |
+upgrade |
This pull request is fully signed and it will be integrated in one of the next CMSSW_10_6_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_11_1_X is complete. This pull request will now be reviewed by the release team before it's merged. @silviodonato, @dpiparo (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
To fix the bug of 2018 premixing wf if start from scratch. BS of 2017 was used. It seems normally, PdmV uses GS from StandardPU wf where BS is handled properly, so the issue has never been spotted. This is to keep the proper configuration of legacy release.
PR validation:
runTheMatrix.py --what premix -l 250200.18 --wm init
provides proper configuration
if this PR is a backport please specify the original PR and why you need to backport that PR:
Backport of #29401, to keep the proper configuration of Legacy release.