Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[12_3_X] Set concurrent lumis/IOVs in ConfigBuilder if their value is different from default regardless of the number of threads #37446

Merged
merged 2 commits into from Apr 4, 2022
Merged

[12_3_X] Set concurrent lumis/IOVs in ConfigBuilder if their value is different from default regardless of the number of threads #37446

merged 2 commits into from Apr 4, 2022

Commits on Mar 29, 2022

  1. Set concurrent lumis/IOVs if their value is different from default re… 

    …gardless of the number of threads

It can happen that the job configuration is generated with cmsDriver
without specifying the number of threads (i.e. that is 1), and ends up
being used with number of threads being overridden. If the number of
concurrent lumis/IOVs is set different from the default in such case,
that setting would be lost.
    @makortel
    makortel committed Mar 29, 2022
    Copy the full SHA
    ee5fe88 View commit details
    Browse the repository at this point in the history

Commits on Apr 1, 2022

  1. Remove setting of DQMStore.assertLegacySafe as unnecessary 

    This parameter was set to False already in
cms-sw#34366.
    @makortel
    makortel committed Apr 1, 2022
    Copy the full SHA
    0f636f3 View commit details
    Browse the repository at this point in the history