-
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
Set numberOfConcurrentLuminosityBlocks to 1 for GEN steps that have EDModules that are not going to support concurrent lumis #35182
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-35182/25119
|
A new Pull Request was created by @makortel (Matti Kortelainen) for master. It involves the following packages:
@SiewYan, @perrotta, @mkirsano, @Saptaparna, @cmsbuild, @GurpreetSinghChahal, @agrohsje, @alberto-sanchez, @qliphy, @fabiocos, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
test parameters:
|
@cmsbuild, please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-f5d47e/18369/summary.html Comparison SummaryThe workflows 140.53 have different files in step1_dasquery.log than the ones found in the baseline. You may want to check and retrigger the tests if necessary. You can check it in the "files" directory in the results of the comparisons Summary:
|
I inspected the GEN step configuration files, and the following workflows set the
|
Thanks @makortel. There is also the pt and dxy gun we could add: Pythia8PtAndDxyGun . |
…DModules that are not going to support concurrent lumis
b777388
to
ab8c522
Compare
Thanks, added. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-35182/25231
|
Pull request #35182 was updated. @SiewYan, @perrotta, @mkirsano, @Saptaparna, @cmsbuild, @GurpreetSinghChahal, @agrohsje, @alberto-sanchez, @qliphy, @fabiocos, @davidlange6 can you please check and sign again. |
@cmsbuild, please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-f5d47e/18558/summary.html Comparison SummarySummary:
|
+generators |
+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. |
PR description:
As reported in #25090 several generator EDModules are not planned to be made support concurrent lumis (e.g. too difficult, so little overal CPU time spent so that it is not worth it, or with
ExternalGeneratorFilter
desire to continue testing generators also directly).In order to silence the warning message on multithreaded jobs, and to later allow changing that warning to an exception (to better prevent any modules that do not support concurrent lumis to creep in workflow steps that are expected to support concurrent lumis), following the example of #35073 this PR suggest the ConfigBuilder to set the number of concurrent lumis (and IOVs) explicitly to 1 if the job has
GEN
step with any of the generator EDModules that do not support concurrent lumis. In this PR I added a new fileConfiguration/Generator/python/concurrentLumisDisable.py
to contain the list of the EDModules (so that it would be explicitly maintained by @cms-sw/generators-l2), in principle they could be listed elsewhere too.This PR is very similar to
PR validation:
Workflows
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
set their GEN step to use 1 concurrent lumi, and workflow10024.0
continues to set 2 concurrent lumis (when run multithreaded).