Skip to content
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

DQM/Tracking: Improve the per-lumi fix [10_6_X] #27239

Merged

Conversation

schneiml
Copy link
Contributor

@schneiml schneiml commented Jun 18, 2019

PR description:

The fix for double counting in a0c43f3 seems to be a bit aggressive. It seems to have reset some MEs that are not per-lumi, so check for that.

PR validation:

Bin-to-bin comparison shows the plots in question re-populated.

if this PR is a backport please specify the original PR:

This is used instead of #27237, and a backport of #27246.

It seems to have reset some MEs that are not per-lumi, so check for that.
@schneiml
Copy link
Contributor Author

please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Jun 18, 2019

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-run-pr-tests/1010/console Started: 2019/06/18 18:06

@cmsbuild
Copy link
Contributor

A new Pull Request was created by @schneiml (Marcel Schneider) for CMSSW_10_6_X.

It involves the following packages:

DQM/TrackingMonitorClient

@andrius-k, @kmaeshima, @schneiml, @cmsbuild, @jfernan2, @fioriNTU can you please review it and eventually sign? Thanks.
@hdelanno, @makortel, @mtosi, @fioriNTU, @jandrea, @idebruyn, @threus this is something you requested to watch as well.
@davidlange6, @slava77, @fabiocos you are the release manager for this.

cms-bot commands are listed here

@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

Comparison job queued.

@cmsbuild
Copy link
Contributor

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

Comparison Summary:

  • No significant changes to the logs found
  • Reco comparison results: 0 differences found in the comparisons
  • DQMHistoTests: Total files compared: 33
  • DQMHistoTests: Total histograms compared: 3208236
  • DQMHistoTests: Total failures: 197
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 3207705
  • DQMHistoTests: Total skipped: 334
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 0.0 KiB( 32 files compared)
  • Checked 137 log files, 14 edm output root files, 33 DQM output files

@mtosi
Copy link
Contributor

mtosi commented Jun 18, 2019

yes, thanks !
I’m afraid the current checks miss the Client to be run, though

@fioriNTU
Copy link
Contributor

I would vote this solution and drop #27237. @mtosi, you are right, the clients are not tested in the current procedure, but probably @hbecerri can perform a quick private test, I know he has everything in place for it.

@schneiml
Copy link
Contributor Author

Looks good, I'd say: http://tinyurl.com/yyanjesa

The changes seem identical between the two PRs, but then it is well possible that we don't run all the features in the PR tests.

@fabiocos
Copy link
Contributor

@schneiml @fioriNTU please recall that before discussing backports we need to have a PR in master.

@schneiml
Copy link
Contributor Author

@fabiocos so far these where only experiments.

@hbecerri
Copy link
Contributor

Hello @fioriNTU, I did the test in my own terminal and the plots look good with the new changes.

@schneiml schneiml changed the title DQM/Tracking: Improve the per-lumi fix DQM/Tracking: Improve the per-lumi fix [10_6_X] Jun 19, 2019
@mmusich
Copy link
Contributor

mmusich commented Jun 21, 2019

@andrius-k, @kmaeshima, @schneiml, @cmsbuild, @jfernan2, @fioriNTU
what is preventing this from beign signed?

@mmusich
Copy link
Contributor

mmusich commented Jun 25, 2019

gentle reminder, shall this be signed as well?

@fioriNTU
Copy link
Contributor

+1

@cmsbuild
Copy link
Contributor

This pull request is fully signed and it will be integrated in one of the next CMSSW_10_6_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_11_0_X is complete. This pull request will now be reviewed by the release team before it's merged. @davidlange6, @slava77, @smuzaffar, @fabiocos (and backports should be raised in the release meeting by the corresponding L2)

@fabiocos
Copy link
Contributor

fabiocos commented Jul 2, 2019

+1

as requested by Tracker/Tracking and PPD

@cmsbuild cmsbuild merged commit 141105a into cms-sw:CMSSW_10_6_X Jul 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants