Muon dqm mini aod 81

[sscruz]

No description provided.

[cmsbuild]

A new Pull Request was created by @sscruz for CMSSW_8_1_X.

It involves the following packages:

DQMOffline/Configuration
DQMOffline/Muon

@cmsbuild, @vanbesien, @deguio, @davidlange6 can you please review it and eventually sign? Thanks.
@barvic, @battibass, @threus, @abbiendi, @jhgoh, @bellan, @trocino, @rociovilar this is something you requested to watch as well.
@slava77, @Degano, @smuzaffar you are the release manager for this.

cms-bot commands are list here #13028

[deguio]

please test

[cmsbuild]

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/12741/console

[cmsbuild]

+1
Tested at: 74fe609
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-14059/12741/summary.html

[cmsbuild]

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

[cmsbuild]

Pull request #14059 was updated. @cmsbuild, @dmitrijus, @vanbesien, @davidlange6 can you please check and sign again.

[dmitrijus]

+1

[cmsbuild]

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/16114/console

[cmsbuild]

This pull request is fully signed and it will be integrated in one of the next CMSSW_8_1_X IBs after it passes the integration tests. This pull request requires discussion in the ORP meeting before it's merged. @slava77, @davidlange6, @smuzaffar

[cmsbuild]

+1
Tested at: 1a3afe3
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-14059/16114/summary.html

[cmsbuild]

Comparison job queued.

[cmsbuild]

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

[folguera]

@slava77, @davidlange6, @smuzaffar, could you please check and approve?

[davidlange6]

+1
@Dr15Jones - please confirm that this does not cause scheduling issues in DEVEL in the next IB...

[Dr15Jones]

In theory, the schedule validator in CMSSW_8_1 should identify cases that would cause problems in _DEVEL and thrown an exception. Unfortunately, there are some know cases it can miss. However, the crux of the problems are

• a module on a Path needs data that only comes from an EndPath or
• a module on a Path wants to get the TriggerResults from this job

As far as I can tell, neither of those appears to be the case for changes from this pull request.