Add the HGCAL-Seeded ElectronSeed collection to the FEVT and RECO event contents. [93X]

[kpedro88]

Backport of #20368

[kpedro88]

please test

[cmsbuild]

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/22758/console Started: 2017/09/06 18:25

[cmsbuild]

A new Pull Request was created by @kpedro88 (Kevin Pedro) for CMSSW_9_3_X.

It involves the following packages:

TrackingTools/Configuration

@perrotta, @cmsbuild, @slava77 can you please review it and eventually sign? Thanks.
@makortel, @felicepantaleo, @GiacomoSguazzoni, @rovere, @VinInn, @bellan, @gpetruc, @ebrondol, @dgulhan this is something you requested to watch as well.
@davidlange6, @slava77 you are the release manager for this.

cms-bot commands are listed here

• Backported from Add the HGCAL-Seeded ElectronSeed collection to the FEVT and RECO event contents. #20368

[kpedro88]

assign upgrade

[cmsbuild]

New categories assigned: upgrade

@kpedro88 you have been requested to review this Pull request/Issue and eventually sign? Thanks

[cmsbuild]

+1
Tested at: b6657cf
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-20407/22758/summary.html

The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic:
b9e4992
You can see more details here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-20407/22758/git-log-recent-commits
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-20407/22758/git-merge-result

[cmsbuild]

Comparison job queued.

[cmsbuild]

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

Comparison Summary:

• No significant changes to the logs found
• Reco comparison results: 0 differences found in the comparisons
• DQMHistoTests: Total files compared: 26
• DQMHistoTests: Total histograms compared: 2656498
• DQMHistoTests: Total failures: 207
• DQMHistoTests: Total nulls: 0
• DQMHistoTests: Total successes: 2656102
• DQMHistoTests: Total skipped: 189
• DQMHistoTests: Total Missing objects: 0
• Checked 107 log files, 14 edm output root files, 26 DQM output files

[kpedro88]

+1

[perrotta]

#20368 is already included in the latest 93X IB (CMSSW_9_3_X_2017-09-06-2300); therefore this backport can be closed.

[slava77]

#20368 is already included in the latest 93X

that PR is also in CMSSW_9_4_X_2017-09-06-2300
@smuzaffar @davidlange6
Was it an intended behavior for just one IB, or will it continue for more?

[smuzaffar]

@slava77 , @perrotta #20368 is only in 94X. Looks like there is bug in the script which generate the IB pages that is why it is showing that #20368 is psrt of 93X. I will check this tomorrow.

[slava77]

CMSSW_9_3_X_2017-09-06-1100...CMSSW_9_3_X_2017-09-06-2300
shows that #20368 is in CMSSW_9_3_X_2017-09-06-2300.
So, I don't think it's the showIB to blame.

[smuzaffar]

but I do not see the changes here in https://github.com/cms-sw/cmssw/commits/CMSSW_9_3_X/TrackingTools/Configuration/python/TrackingTools_EventContent_cff.py.

Ah my bad, 93X is still using master branch to tag. I am fixing it and re-building 93X IB now.

[kpedro88]

@smuzaffar does this mean this PR should be closed or not? What about #20408?

[smuzaffar]

@kpedro88 , no both of these should remain open if they are meant for 93X (they are not in 93X yet). I will check if I can fix showIB to ignore 93X 06-1100 and 06-2300 IBs to get the correct PRs list which went in to 93X

[perrotta]

+1
Identical to #20368, merged in 93X

[cmsbuild]

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

[davidlange6]

+1