-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
segmentation violation in L1TStage2CaloLayer1 #32172
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 |
I confirm that |
ahh ... alright :) but I was running a failing workflow earlier which passed and this puzzles me. |
Shahzad started a new IB h1600 with #32173 |
For reference, this is the full list of the crashing workflows
|
@silviodonato I'm sorry, I'm just seeing this now. I will admit myself confused. This passed both the build tests, and I tested it myself personally in the online configurations and using I had tested it with:
But it seems like your command has:
I assume the difference between these two is an invocation of multiple streams? What all do I need to do to recreate this segfault, and when I have it fixed, how should I reopen the PR to get this fixed? Thanks, |
Hi @aloeliger , yes, you can recreate the issue by running with multithreading (eg. using |
Okay I've isolated the problem. It seems like it was a stack overflow caused by my poorly written binary search for mismatch location in the final list at the end of a stream. I'm working on a fix for it now, but this may not be the only issue present. |
Hello all, I have opened a PR I believe addresses and fixes these issues, which runs Out of curiosity, and for the future, are there multi-threaded validation options for the cmsbuild bot that I could have used to avoid committing this error? |
Unfortunately no, the PR tests are single-threaded on purpose (to guarantee easily fully reproducible simulation results). |
Done by #32205 |
202 workflows crashed in
CMSSW_11_2_X_2020-11-17-2300
.For instance step3 of wf 136.721 get segmentation violation
The offending PR is #32004
The text was updated successfully, but these errors were encountered: