flood of "Electron ID handle not valid " in Top DQM

[slava77]

e.g. in wf 136.85
https://cmssdt.cern.ch/SDT/jenkins-artifacts/ib-baseline-tests/CMSSW_10_3_X_2018-08-22-2300/slc6_amd64_gcc700/-GenuineIntel/matrix-results/136.85_RunEGamma2018A+RunEGamma2018A+HLTDR2_2018+RECODR2_2018reHLT_skimEGamma_Prompt_L1TEgDQM+HARVEST2018_L1TEgDQM/step3_RunEGamma2018A+RunEGamma2018A+HLTDR2_2018+RECODR2_2018reHLT_skimEGamma_Prompt_L1TEgDQM+HARVEST2018_L1TEgDQM.log

Begin processing the 2nd record. Run 315489, Event 47708809, LumiSection 78 on stream 0 at 23-Aug-2018 04:54:24.737 CEST
...
%MSG-w TopMonitor:  TopMonitor:mu12TrkIsoVVLEle23CaloIdLTrackIdLIsoVLDZ_muleg  23-Aug-2018 04:54:30 CEST Run: 315489 Event: 47708809
Electron ID handle not valid 

there are about 30 such messages per event.

@Sam-Harper you may know a solution

[slava77]

assign dqm

[cmsbuild]

New categories assigned: dqm

@jfernan2,@andrius-k,@schneiml,@kmaeshima you have been requested to review this Pull request/Issue and eventually sign? Thanks

[cmsbuild]

A new Issue was created by @slava77 Slava Krutelyov.

@davidlange6, @Dr15Jones, @smuzaffar, @fabiocos, @kpedro88 can you please review it and eventually sign/assign? Thanks.

cms-bot commands are listed here

[davidlange6]

already discussed in #24155 which was merged regardless.

…

On Aug 23, 2018, at 2:45 PM, Slava Krutelyov ***@***.***> wrote: assign dqm — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[slava77]

already discussed in #24155 which was merged regardless.

ok, that points to the history of the problem, not to a solution, IIUC

[davidlange6]

I guess it points to one solution:) - but right, not a good solution

[Sam-Harper]

yes, I know a solution. Its simply because this ID module this DQM uses isnt running the Fall17 IDs. Give me an hour or so and I'll submit a PR to fix it

[Sam-Harper]

all fixed now: #24379

[fabiocos]

@Sam-Harper thank you for fixing the issue, that unfortunately is not the only one with the PR that introduced originally the problem. I assume that this issue can be closed, while the fix should be back-ported into 10_2_X

[schneiml]

@slava77 sounds like this should be closed.

[slava77]

ok, closing.