-
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
Modify DQMHarvestUnit to multiRun when RD MC runs #29494
Modify DQMHarvestUnit to multiRun when RD MC runs #29494
Conversation
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-29494/14727
|
A new Pull Request was created by @srimanob (Phat Srimanobhas) for master. 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 |
test parameters |
please test |
The tests are being triggered in jenkins.
|
+1 |
Comparison job queued. |
Comparison is ready @slava77 comparisons for the following workflows were not done due to missing matrix map:
Comparison Summary:
|
+1 |
@kpedro88 do you have any objections? |
+upgrade |
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 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:
Following the discussion in https://hypernews.cern.ch/HyperNews/CMS/get/wmDevelopment/808.html
When Multi-Run Harvesting is used, the workflow dictionary needs to be updated:
"DQMHarvestUnit": "byRun", ==> change to "multiRun"
PR validation:
Local test or IB can't validate this PR as local harvesting is running fine. We need to test with submitted workflows. Two relvals have been submitted to test this update:
One can just trigger the test with RD workflow, i.e. 250200.182 just to see local run is fine.
In addition, the above workflows will validate also issue reported in #29472 (Strange output when firstLuminosityBlockForEachRun is used for Run-Dependent MC)
if this PR is a backport please specify the original PR and why you need to backport that PR: