-
-
Notifications
You must be signed in to change notification settings - Fork 74
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 fault on Jenkins since Zope 5.11 #962
Comments
You can trigger it with plone.app.testing:
|
@mauritsvanrees Can't reproduce on my M1 Mac. Could you run the same command under gdb to get a C-level stack trace? |
I have not used But I tracked it down to When I checkout |
@mauritsvanrees It's pretty simple, you just run Anyway, my money was on zope.interface. (Easy for me to place my bet after I know the answer!) There have been several different segfaults resulting from recent refactoring to support free-threading in Python 3.13. The most recent was just merged yesterday (zopefoundation/zope.interface#324) but not yet released so I expect that's why it works when you use a checkout. |
This is fixed in |
I upgraded coredev 6.1 to Zope 5.11 today in #959. All tests were reported as green. And indeed the robot tests passed, which is good news, but after that there was a segmentation fault. Actually there were two segmentation faults, one when running the non-robot tests, and one after running the robot tests.
So Jenkins did not properly report a problem. Maybe the segmentation fault is the cause.
As a start I will revert to Zope 5.10.
The text was updated successfully, but these errors were encountered: