-
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
Fix BeamMonitor names in BeamSpot DQM clients #34467
Conversation
Thanks @francescobrivio ! |
Ok I will open the backport it in 2 minutes then! |
please test |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-34467/23918
|
A new Pull Request was created by @francescobrivio for master. It involves the following packages:
@andrius-k, @kmaeshima, @ErnestaP, @ahmad3213, @jfernan2, @rvenditti can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-9e84e0/16768/summary.html Comparison SummarySummary:
|
+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 now be reviewed by the release team before it's merged. @silviodonato, @dpiparo, @qliphy, @perrotta (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
This PR fixes the
dqmEnv.subSystemFolder
,dqmSaver.tag
anddqmSaverPB.tag
names in the BeamMonitor (and FakeBeamMonitor), so that when running the two clients in parallel the output root files are named differently and no crash should happen in DQM at the file-merging step.PR validation:
I run locally the unit tests to confirm that the output names of the root files are changed as expected.
For example:
@jfernan2 I'm not sure how to test the change done for
dqmEnv.subSystemFolder
, any suggestion?if this PR is a backport please specify the original PR and why you need to backport that PR:
Backported in #34468