-
Notifications
You must be signed in to change notification settings - Fork 183
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
SegFaults in TensorFlow usage by L1TMuonEndCapTrackProducer #6618
Comments
An example stack trace can be seen here:https://cmssdt.cern.ch/SDT/cgi-bin/logreader/slc7_amd64_gcc900/CMSSW_11_3_X_2021-02-03-0800/pyRelValMatrixLogs/run/136.779_RunMuOnia2016H+RunMuOnia2016H+HLTDR2_2016+RECODR2_2016reHLT_skimMuOnia_Prompt+HARVESTDR2/step2_RunMuOnia2016H+RunMuOnia2016H+HLTDR2_2016+RECODR2_2016reHLT_skimMuOnia_Prompt+HARVESTDR2.log#/214-214
|
assign l1 |
A new Issue was created by @Dr15Jones Chris Jones. @Dr15Jones, @dpiparo, @silviodonato, @smuzaffar, @makortel, @qliphy can you please review it and eventually sign/assign? Thanks. cms-bot commands are listed here |
integration of cms-sw/cmssw#32641 and cms-data/L1Trigger-L1TMuon#19 might be the reason behind these failures |
this was fixed ? |
@mrodozov yes this specific instance is fixed. Although there is still a discussion ongoing in cms-sw/cmssw#32894. |
closing this in favor of cms-sw/cmssw#32894 issue |
In CMSSW_11_3_X_2021-02-03-0800 we are seeing many release validation jobs failing with segmentation faults coming from the use of TensorFlow called from L1TMuonEndCapTrackProducer.
The text was updated successfully, but these errors were encountered: