-
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
[ASNEEDED_X] Multiple RelVals failing with SIGSEGV #45747
Comments
cms-bot internal usage |
A new Issue was created by @iarspider. @Dr15Jones, @antoniovilela, @makortel, @mandrenguyen, @rappoccio, @sextonkennedy, @smuzaffar can you please review it and eventually sign/assign? Thanks. cms-bot commands are listed here |
Two RelVals - Relval 574.0 step 1 and Relval 577.0 step 1 - failed with
|
assign core |
New categories assigned: core @Dr15Jones,@makortel,@smuzaffar you have been requested to review this Pull request/Issue and eventually sign? Thanks |
FYI @cms-sw/simulation-l2 |
@iarspider , would it be possible to test GEANT4 branch? It uses the most recent Geant4. Even in previous cases OrderingTable should not be opened, in the latest version of G4 both the table and the call to it are removed. |
I am not sure but suspect that there are two problems: in generator there is no needed data and in the Geant4 initialisation data race in destruction in circomstances of incomplete initial initialisation. Proposed PR #45986 may be useful for Geant4 part but cannot fix generator problem. |
It seems that #45986 removes Geant4 warnings/exceptions but generator problems remain. |
Looks like all these workflow require
forcefully linking or preloading
|
Looks like I have split the |
For example Relval 132.0 step 1
Not sure if the error is in Geant4 or Pythia6:
Full stacktrace
Geant4 also reports this exception:
Some RelVals (e.g. 159.03) are reported to fail with SIGABRT, but log indicates that SIGSEGV also occured:
The text was updated successfully, but these errors were encountered: