add two CSCTF plots for debugging MPC/TMB errors from CSC

[rjwang]

add two CSCTF plots for debugging MPC/TMB errors from CSC

[cmsbuild]

A new Pull Request was created by @rjwang (Ren-Jie Wang) for CMSSW_7_5_X.

It involves the following packages:

DQM/L1TMonitor

@cmsbuild, @danduggan, @vanbesien, @deguio, @davidlange6 can you please review it and eventually sign? Thanks.
@Degano you are the release manager for this.

Following commands in first line of a comment are recognized

• +1|approve[d]|sign[ed]: L1/L2's to approve it
• -1|reject[ed]: L1/L2's to reject it
• assign <category>[,<category>[,...]]: L1/L2's to request signatures from other categories
• unassign <category>[,<category>[,...]]: L1/L2's to remove signatures from other categories
• hold: L1/all L2's/release manager to mark it as on hold
• unhold: L1/user who put this PR on hold
• merge: L1/release managers to merge this request
• [@cmsbuild,] please test: L1/L2 and selected users to start jenkins tests
• [@cmsbuild,] please test with cms-sw/cmsdist#<PR>: L1/L2 and selected users to start jenkins tests using externals from cmsdist

[deguio]

please test

[deguio]

+1
provided it passes the tests

[cmsbuild]

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

[cmsbuild]

This pull request is fully signed and it will be integrated in one of the next CMSSW_7_5_X IBs after it passes the integration tests and once validation in the development release cycle CMSSW_7_6_X is complete. This pull request requires discussion in the ORP meeting before it's merged. @davidlange6, @Degano, @smuzaffar

[cmsbuild]

+1
Tested at: a9c2a33
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-12470/9802/summary.html

[cmsbuild]

This pull request is fully signed and it will be integrated in one of the next CMSSW_7_5_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_7_6_X is complete. This pull request requires discussion in the ORP meeting before it's merged. @davidlange6, @Degano, @smuzaffar

[cmsbuild]

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

[cmsbuild]

This pull request is fully signed and it will be integrated in one of the next CMSSW_7_5_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_7_6_X is complete. This pull request requires discussion in the ORP meeting before it's merged. @davidlange6, @Degano, @smuzaffar

[deguio]

unfortunately this PR doesn't merge on top of #12505
please rebase on top of that branch

[rjwang]

Does that mean we have to remake a PR with the latest release?

On Nov 22, 2015, at 12:42 PM, Federico De Guio [email protected] wrote:

unfortunately this PR doesn't merge on top of #12505 #12505
please rebase on top of that branch

—
Reply to this email directly or view it on GitHub #12470 (comment).

[slava77]

#12505 isn't merged yet. It's not a matter of using the latest release. Two PRs (this and #12505 ) conflict with each other.

[rjwang]

Then, what should I do from my side? can I see where is the conflict, and we do need this PR to be merged asap in order to help CSC debug any problems in the trigger path.

On Nov 23, 2015, at 9:00 AM, Slava Krutelyov [email protected] wrote:

#12505 #12505 isn't merged yet. It's not a matter of using the latest release. Two PRs (this and #12505 #12505 ) conflict with each other.

—
Reply to this email directly or view it on GitHub #12470 (comment).

[slava77]

@deguio is this PR ready to go to 75X?
it sounds like you may have a higher priority for #12505 (else the issue of merging conflicts in #12470 (comment) doesn't seem clear).
Please clarify.
Thanks.

[deguio]

ciao @slava77
I believe that this one can be merged and #12505 can be rebased on top on the head.

this is a warning for @jingyucms

[slava77]

merge

it's unclear when we make a new release though
[80X IBs were apparently OK with #12472 ]

[rjwang]

Thanks.

On Nov 24, 2015, at 10:03 AM, Slava Krutelyov [email protected] wrote:

merge

it's unclear when we make a new release though

—
Reply to this email directly or view it on GitHub #12470 (comment).