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
random segfaults in linear_tensor_element.pyx #28559
Comments
This comment has been minimized.
This comment has been minimized.
comment:3
No one proposes a solution. How about adopting John's temporary measure here just to push sage on python 3? We can create a regular ticket to further track the issue. |
comment:4
Indeed, this also happening with LinuxMint: There is no urgency to fix this for python3. The switch to python3 will happen very soon anyway. |
Changed keywords from none to random_fail |
comment:6
I'm still surprised this isn't similar or related to #28106. Memory exhaustion is the most likely culprit for random failures like this. |
comment:7
I think there is an underlying memory corruption bug here.
|
comment:8
Ticket retargeted after milestone closed |
comment:9
Moving tickets to milestone sage-9.2 based on a review of last modification date, branch status, and severity. |
comment:11
Setting new milestone based on a cursory review of ticket status, priority, and last modification date. |
comment:13
I haven't seen this problem in a long time. Has anyone else? |
comment:14
Yes, this happened on the NixOS builders yesterday: https://nix-cache.s3.amazonaws.com/log/npaj3152j2q7nq1n58i8sncx57mkf6g3-sage-tests-9.2.drv |
comment:15
It's easy to find examples of thread-safety issues related to GLPK in other projects, such as jyp/glpk-hs#9. I don't know how Cython's |
comment:16
Replying to @jhpalmieri:
A few days ago, this happened on a patchbot with Debian. |
Just seen in the Conda CI (ubuntu, 3.10) https://github.com/sagemath/sage/actions/runs/7258182411/job/19773109005?pr=36916#step:11:7010 |
Intermittent failure with
linear_tensor_element.pyx
on OS X with a Python 3 build of Sage:In more detail:
This has been discussed at #27587, but I think it deserves its own ticket. For some reason, this change makes the failure go away:
but I don't know why.
CC: @collares
Component: python3
Keywords: random_fail
Issue created by migration from https://trac.sagemath.org/ticket/28559
The text was updated successfully, but these errors were encountered: