HLT DQM for 9.3.x - part 3 #19891
HLT DQM for 9.3.x - part 3 #19891
Conversation
…uired changing the top source code
Fixed conflicts: DQMOffline/Trigger/python/ExoticaMonitoring_cff.py
Conflicts: DQMOffline/Trigger/python/SusyMonitoring_Client_cff.py DQMOffline/Trigger/python/SusyMonitoring_cff.py
|
@cmsbuild, please test |
|
The tests are being triggered in jenkins. |
|
A new Pull Request was created by @fwyzard (Andrea Bocci) for master. It involves the following packages: DQMOffline/Trigger @vazzolini, @kmaeshima, @dmitrijus, @cmsbuild, @vanbesien, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
|
+1 The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic: |
|
Comparison job queued. |
|
Thanks. For more HLT DQM, do I open a new PR to or keep merging things here ? |
|
merge |
|
i meant to merge this. |
|
hi @fwyzard - it looks like this PR has introduced a bunch of seg faults - could you find a quick fix eg ----- Begin Fatal Exception 25-Jul-2017 14:24:05 CEST----------------------- |
|
will look - just to confirm, these are exceptions, not segfaults we are talkinig about, right ? |
|
If my guess is correct, #19912 should fix these errors. |
|
OK, step3 of 136.784 runs fine with the fix. |
|
@fwyzard |
|
hi @Martin-Grunewald , And by the way, what does the exception mean ? |
|
Yes, also seen in IBs - presumably a problem with StringCutParser setup (perhaps a sign that this code had never selected an event in the developers tests...)
… On Jul 26, 2017, at 8:26 AM, Martin Grunewald ***@***.***> wrote:
@fwyzard
TSG test shows this error:
%MSG
----- Begin Fatal Exception 26-Jul-2017 08:07:55 CEST-----------------------
An exception of category 'StdException' occurred while
[0] Processing Event run: 1 lumi: 3 event: 103 stream: 1
[1] Running path 'dqmofflineOnPAT_step'
[2] Calling method for module TopMonitor/'WprimeEle115'
Exception Message:
A std::exception was thrown.
no method or data member named "deltaEtaSuperClusterAtVtx" found for type "reco::GsfElectron"
----- End Fatal Exception -------------------------------------------------
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
… On Jul 26, 2017, at 8:52 AM, Andrea Bocci ***@***.***> wrote:
hi @Martin-Grunewald ,
how do I reproduce it ?
And by the way, what does the exception mean ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
hi @davidlange6 , do you want the fix on top of #19916 or stand-alone ? |
|
Stand alone please
… On Jul 26, 2017, at 9:50 AM, Andrea Bocci ***@***.***> wrote:
hi @davidlange6 , do you want the fix on top of #19916 or stand-alone ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
Using #19918 I get the next error: |
|
Sigh... on which workflow? |
|
Our TSG workflow on the V2.1 menu - within |
|
hi again, However, for my tests I've used #19916 (actually #19917) on top of the other changes. Is it possible that the problem has already been fixed by the commits there ? Martin, can you try with the latest IB + #19917 ? |
|
@fwyzard to reproduce: make a developer area: The first cmsRun takes a GEN-SIM file and produces the file needed for the second cmsRun which shows the crash. |
|
Your test machine is bigger than mine... In my second attempt, the job was killed after the first few events by the kernel because the machine ran out of memory. In the first attempt the whole machine died... I'm trying again with a singe stream to reduce the memory usage. |
|
OK, with a single thread/stream I can reproduce the error. |
Follow up to #19713.
Merge the following HLT DQM pull requests (in this order):