Seg Faults with PyPy #2781
-
I'm seeing intermittent but (I think) increasing common segmentation faults with pypy on CI. Builds examples:
The error appears at the end of running tests, and output generally looks something like:
Any idea what's going on here? I'm not suggesting this is an issue with pyo3, but not sure where else to ask. I saw seg faults early on with pypy when pushing deep recursive validation models, but once I set a lower threshold for recursion in pypy the errors stopped (well paused, as they're happening again). However these errors are happening when pytest finished, not on the recursion tests. So I'm a bit stumped. |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 16 replies
-
Try use the tmate action to obtain and inspect the core dump file? - uses: mxschmitt/action-tmate@v3
if: failure() |
Beta Was this translation helpful? Give feedback.
-
Sorry I missed this. We just got a report to the PyPy issue tracker where pydantic core tests crash when built in dev mode. Maybe related, maybe something else? I do see that there are test failures in dev mode when I skip the segfault-ing tests
This comes from |
Beta Was this translation helpful? Give feedback.
-
I think I have a resolution for this in pydantic/pydantic-core#744 |
Beta Was this translation helpful? Give feedback.
@samuelcolvin The following diff fixes the stack overflows / segmentation faults for (but it leads to assertion errors as the assertions depend on the depth limit):