-
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
(DAQ) fix input source cv notification [14_1_X] #44979
Conversation
…l with file rate beyond 10 Hz)
cms-bot internal usage |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-44979/40260
|
A new Pull Request was created by @smorovic for master. It involves the following packages:
@cmsbuild, @smorovic, @emeschi can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@cmsbuild please test |
-1 Failed Tests: RelVals-INPUT RelVals-INPUT
Comparison SummarySummary:
|
@cmsbuild please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-29fe0e/39397/summary.html Comparison SummarySummary:
|
+daq |
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. @rappoccio, @sextonkennedy, @antoniovilela (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
Bugfix for DAQ input sources fixing the issue where notification via condition variable is not passed between threads, resulting in acting only after a timeout of 0.1s.
Generally not a problem in data taking, but was limiting file rate to 10Hz and was a limitation in high-rate MiniDAQ runs.
Applied also to DAQSource (used for scouting) where same logic is used.
PR validation:
Tested in live miniDAQ system with a patched CMSSW version