Fix premature end of run in DAQ (76X)

[smorovic]

In case of multiple pending lumisections in builder unit (ramdisk), recently forced behavior is to cycle the framework through each LS (previously source was skipping to the last one, in case on raw data needs to be processed). This change uncovered a loophole in logic allowing run to end prematurely if end of run file (written by BU) is in ramdisk, but there is still at least two empty lumisections and then some data to process.
Fix is to allow the run to be closed only if no new files/lumisections have been discovered by source after EoR file has already been written to the input directory.

This change was submitted in 74X as #11156 and in 75X as #11157

[cmsbuild]

A new Pull Request was created by @smorovic (Srecko Morovic) for CMSSW_7_6_X.

Fix premature end of run in DAQ (76X)

It involves the following packages:

EventFilter/Utilities

@mommsen, @cvuosalo, @cmsbuild, @emeschi, @slava77 can you please review it and eventually sign? Thanks.
@Martin-Grunewald this is something you requested to watch as well.
You can sign-off by replying to this message having '+1' in the first line of your reply.
You can reject by replying to this message having '-1' in the first line of your reply.
If you are a L2 or a release manager you can ask for tests by saying 'please test' in the first line of a comment.
@Degano you are the release manager for this.
You can merge this pull request by typing 'merge' in the first line of your comment.

[davidlange6]

@cmsbuild, please test

[cmsbuild]

The tests are being triggered in jenkins.

[cmsbuild]

+1
Tested at: c50fee9
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-11158/7916/summary.html

[cmsbuild]

Comparison is ready
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-11158/7916/summary.html

[cvuosalo]

+1

For #11158 c50fee9

Bug fix related to lumi sections. There should be no change in monitored quantities. #11156 and #11157 are the 74X and 75X versions of this PR, and they have both been already approved by Reco.

The code change is satisfactory, and Jenkins tests against baseline CMSSW_7_6_X_2015-09-06-2300 show no significant differences, as expected.