-
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
Update run for DQM beamhlt client unitTest #38925
Update run for DQM beamhlt client unitTest #38925
Conversation
test parameters: |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-38925/31372
|
A new Pull Request was created by @francescobrivio for master. It involves the following packages:
@emanueleusai, @ahmad3213, @cmsbuild, @jfernan2, @pmandrik, @micsucmed, @rvenditti can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
I can see already from the unitTest log that the warning is now gone. |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-f287e4/26587/summary.html The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic:
You can see more details here: Comparison SummaryThere are some workflows for which there are errors in the baseline: Summary:
|
This is absolutely unrelated and irrelevant to this PR. |
+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. @perrotta, @dpiparo, @qliphy, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
@francescobrivio @emanueleusai |
@qliphy the unit test fails for PPS, this PR didnt touch PPS, so it's not coming from here |
@qliphy this PR only touches the unitTest of the |
PR description:
This PR updates the run used for the DQM
beamhlt
client unitTest (introduced in #37667) in order to get rid of the warnings emitted when running with the current input streamer files:as can be seen, for example, in the IB unitTest results.
With this PR the warning message is gone.
PR validation:
scram b runtests
runs fineIf 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:
Not a backport, no backport needed since this does not affect data-taking.