-
Notifications
You must be signed in to change notification settings - Fork 5
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
Assertion failed in CPU version of kernel_countMultiplicity #392
Comments
FYI @VinInn |
would be interesting to understand if it is reproducible (at event level). |
It's not very reproducible. As I wrote in the description, it occurred once in 44 executions (with varying number of streams/threads). I could of course try to repeat it (with high thread count).
Real, from the LS 142 of run 321177 from 2018D JetHT ("the usual"). |
On a closer inspection I found another assertion failure in the logs of the 44 jobs. It was certainly a different event
(this was on 80-stream/thread job) |
Hmm, I just repeated 80-stream/thread job for 150 times, no failures. |
The CPU workflow is supposed to be thread safe (but the stats (not used in perfWf) that I have still to fix (require proper handling of AtomicAdd)) |
While running the CPU profiling workflow (
customizePixelTracksSoAonCPUForProfiling()
) on 11_0_0_pre7_Patatrack at NERSC, I got an assertion failurewhen running on 64 streams/threads. This failure occurred only once though during my tests on 4x{1, 16, 32}, 10x64, 4x{1, 20, 40}, and 10x80 streams/threads, but I thought to report it anyway ("NxM" meaning "N runs of M streams/threads").
The text was updated successfully, but these errors were encountered: