-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
[13_2_X] Fix random DQM path order from ConfigBuilder in case of duplicate DQM sequences #42834
[13_2_X] Fix random DQM path order from ConfigBuilder in case of duplicate DQM sequences #42834
Conversation
… sequences PromptReco for Heavy Ions was generating different RECO configurations for each job of the same Primary Dataset (and Run). This caused problems during merging as the ParameterSet registry grew. The difference between the RECO configurations was in how the DQM sequences were assigned to DQM Paths. One source for random shuffling was found to be in ConfigBuilder in case the expansion of the DQM sequence specifier leads to duplicate sequences. This commit fixes the path ordering, and adds a test for it. Co-authored-by: Christopher Jones <[email protected]>
A new Pull Request was created by @makortel (Matti Kortelainen) for CMSSW_13_2_X. It involves the following packages:
@cmsbuild, @antoniovilela, @rappoccio, @fabiocos, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@cmsbuild, please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-fc7b15/34843/summary.html Comparison SummarySummary:
|
urgent |
backport of #42833 |
+1 |
This pull request is fully signed and it will be integrated in one of the next CMSSW_13_2_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_13_3_X is complete. This pull request will be automatically merged. |
PR description:
Backport of #42833. Original description
PR validation:
The added unit test succeeds (and failed without the fix)
If this PR is a backport please specify the original PR and why you need to backport that PR. If this PR will be backported please specify to which release cycle the backport is meant for:
Backport of #42833