fix closing lumisection in HLT(DAQ) when stop requested for Cloud switchover (80X) #14125
Conversation
…ndition that does not happen normally, but is a result of some other problem), LS value given by CMSSW_STOP file (created by hltd usually when cloud switch is made mid-run) is older than the current LS processed by CMSSW. In that case it was possible to end run in the mid of current LS, which rarely resulted in not writing EoLS file to disk and thus causing lumisection to remain unmerged on FU. This patch sets higher "stop LS" if in such condition.
|
A new Pull Request was created by @smorovic (Srecko Morovic) for CMSSW_8_0_X. It involves the following packages: EventFilter/Utilities @cvuosalo, @emeschi, @cmsbuild, @slava77, @mommsen, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are list here #13028 |
|
+1 |
|
The tests are being triggered in jenkins. |
|
+1 The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic: |
|
Comparison is ready The workflows 1003.0, 134.911 have different files in step1_dasquery.log than the ones found in the baseline. You may want to check and retrigger the tests if necessary. You can check it in the "files" directory in the results of the comparisons |
Fix for a bug appearing with high ramdisk access latency
(exceptional condition that does not happen normally, but is a result of some other problem, usually network / NFS) whene LS value given by CMSSW_STOP file
(created by hltd usually when cloud switch is made mid-run) is older than the current LS processed by CMSSW.
In this condition, end run in can happen in the mid of current LS, which
rarely resulted in not writing EoLS file to disk and thus causing lumisection to remain unmerged on FU.
This patch sets higher "stop LS" value with which current LS is properly closedr (EoLS file gets written out as in the usual case).