-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
DQMOnlineClient-beam_dqm_sourceclient error #31896
Comments
A new Issue was created by @silviodonato Silvio Donato. @Dr15Jones, @dpiparo, @silviodonato, @smuzaffar, @makortel, @qliphy can you please review it and eventually sign/assign? Thanks. cms-bot commands are listed here |
assign DQM |
assign dqm |
New categories assigned: dqm @jfernan2,@andrius-k,@fioriNTU,@kmaeshima,@ErnestaP you have been requested to review this Pull request/Issue and eventually sign? Thanks |
we don't see the error in |
this is the second time I see this error being revived in a PR Jenkins test: 26-Nov-2020 11:04:32 CET Successfully opened file root://eoscms.cern.ch//eos/cms/store/user/cmsbuild/store/express/Commissioning2019/ExpressCosmics/FEVT/Express-v1/000/334/393/00000/FE21789A-F777-0B43-A1F5-E43F1FD52D19.root Fatal system signal has occurred during exit ---> test TestDQMOnlineClient-beam_dqm_sourceclient had ERRORS |
What I am not sure if this is related to the SiStripRawToDigiModule:siStripDigis Warning before (it seems not since that warning is present in several other unit Tests) or to the beam_dqm_sourceclient itself I have just tried to reproduce it using exactly same settings as in #32036 but failed, however perhaps it makes sense to reopen this issue since it seems to be there FYI: @gennai @francescobrivio |
@jfernan2
the warning comes from the Strip unpacker and just signals there is one or more FED(-s) out of DAQ [1] (1800 is the number of times the same warning is emitted) . [1] https://github.com/cms-sw/cmssw/blob/master/EventFilter/SiStripRawToDigi/plugins/SiStripRawToDigiUnpacker.cc#L158 |
Thanks @mmusich |
Another one example: #27983 (comment) |
I would exclude that 11_3_X can cause this problem. Googling "Fatal system signal has occurred during exit" I've found a @makortel issue #32045 |
The same error was seen here #31190 (comment) |
The error
It runs without errors in It crashes in
|
assign db |
New categories assigned: db @ggovi you have been requested to review this Pull request/Issue and eventually sign? Thanks |
@silviodonato Does the crash in ASAN have any information in addition to the "Fatal system signal during exit"? (if it does, could you paste it here?) |
No, there is no additional information (see https://cmssdt.cern.ch/SDT/cgi-bin/logreader/slc7_amd64_gcc820/CMSSW_11_2_ASAN_X_2020-11-25-2300/unitTestLogs/DQM/Integration#/51) |
Running Silvio's example configuration #31896 (comment) (thanks!) in gdb in CMSSW_11_2_ASAN_X_2020-11-25-2300 shows a segfault with the following stack trace
|
The following PR should be fixing this somehow: |
I don't think #32408 will fix this issue. It just contains some minor updates of the clients after last MWGR tests. |
Addressed by #32503 |
+1 |
The crash has been solved by #32503 (I tested #31896 (comment) in CMSSW_11_3_ASAN_X_2021-01-06-2300) |
In
CMSSW_11_2_X_2020-10-21-2300
, a unit test fromDQM/Integration
is failing.This was already reported in some PR test (see #31654 (comment)) :
#32135 (comment)
#32036 (comment)
#31765 (comment)
#31871 (comment)
#31699 (comment)
#31689 (comment)
#31654 (comment)
#31206 (comment)
#27983 (comment)
https://cmssdt.cern.ch/SDT/cgi-bin/logreader/cc8_amd64_gcc8/CMSSW_11_2_X_2020-10-21-2300/unitTestLogs/DQM/Integration#/
The text was updated successfully, but these errors were encountered: