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
Intermittent failures in DD4hep test workflow #32646
Comments
assign geometry |
New categories assigned: geometry @Dr15Jones,@cvuosalo,@mdhildreth,@makortel,@ianna,@civanch you have been requested to review this Pull request/Issue and eventually sign? Thanks |
A new Issue was created by @kpedro88 Kevin Pedro. @Dr15Jones, @dpiparo, @silviodonato, @smuzaffar, @makortel, @qliphy can you please review it and eventually sign/assign? Thanks. cms-bot commands are listed here |
@civanch Could you please take a look at these errors? How might they be caused? |
assign simulation |
New categories assigned: simulation @mdhildreth,@civanch you have been requested to review this Pull request/Issue and eventually sign? Thanks |
@civanch I noticed some sporadic errors in my own tests of the workflow last month, so the instability has been present for a while. But the errors were not reproducible. |
This error has been discussed with expert in Geant4 tracking John Apostolakis. It happens due to negative step length -1 mm, which is huge and is not related to precision lost. From my point of view, it is an indication that there is a broken geometry. Position of the initial point (-538.967161 604.098226 -167.072581), particle is e- of 6 keV. John said, that for -1 mm step integration in field may fail, such step length is not allowed. |
(message irrelevant for his issue deleted) |
@makortel we've been seeing the ppc related failure consistently. We really need access to a machine to attempt to debug what is happening. |
Oh, it was PPC, missed that, thanks. Nevermind then (in this issue). |
+1 This is fixed now |
This issue is fully signed and ready to be closed. |
I've seen this issue in unrelated PRs at least twice now:
#32576 (comment)
#32574 (comment)
The text was updated successfully, but these errors were encountered: