-
Notifications
You must be signed in to change notification settings - Fork 113
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
segfault when running the tests #2867
Comments
My current theory is that:
When I have some more time, I'll see if I can confirm the theory |
Got a valgrind trace that summarizes the above:
The reduced set of tests required to trigger it somewhat often (1 in 10 times?) is:
|
@mgeplf : I haven't looked at the code details but not surprised by the global state-related issue. With the code that you have skimmed through, do you know already a potential fix? |
My guess is that one of |
Context
Overview of the issue
I saw the pytest pin, and was wondering if I could get it to happen with the older version of pytest
Expected result/behavior
Not have a segfault
NEURON setup
Commit 8a9bada; python 3.11 from pyenv on Ubuntu 20.04.
If I run it a few times, along with failures, I get a SEGFAULT.
In gdb, I get the following traceback:
The text was updated successfully, but these errors were encountered: