-
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 logic for setting nConcurrentLumis from cmsDriver in favor of similar logic now in cmsRun #35302
Remove logic for setting nConcurrentLumis from cmsDriver in favor of similar logic now in cmsRun #35302
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-35302/25312
|
A new Pull Request was created by @makortel (Matti Kortelainen) for master. It involves the following packages:
@perrotta, @cmsbuild, @qliphy, @fabiocos, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
test parameters:
|
@cmsbuild, please test |
+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 be automatically merged. |
I was supposed to do this at the same time as cms-sw#35302 that followed cms-sw#34231 and the conclusion in cms-sw#33436
PR description:
This PR suggests to remove the logic to set
nConcurrentLumis
based onnStreams
that was introduced in #32406 in favor of similar logic introduced in cmsRun in #34231.Resolves cms-sw/framework-team#260
PR validation:
Inspected the configurations for the matrix workflows
limited,5.2,140.0,521.0,7.0,300.0,140.0,5.5,511.0,281.0,8.1,534.0,281.0,132.0,280.0,120.0
and only the GEN steps specified in #35182 and in ALCA step in 1001.0 (#35073) set theprocess.options.numberOfConcurrentLumis = 1
. All other steps use the default value of0
, which the cmsRun then interprets as "set default value based on the number of streams".