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
Out of memory problem in matrix_mod2_dense.pyx tests on Cygwin #25884
Comments
This comment has been minimized.
This comment has been minimized.
comment:2
Tried the problematic example in a known-good install of Sage 8.2 with no problems. |
comment:3
In fact, it's probably not that example that's the problem, but an earlier one, and the above example is just where I happen to finally run out of memory. There must be a memory leak elsewhere. The test passes on a machine with more memory (e.g. my work machine), but it takes a very long time due to the memory leak. That's possibly why I haven't noticed before. |
comment:4
Yes, the problem is the memory overflow tests that have come up before, e.g. in #24190. And the problem is that even if the test passes, as it did in this case, there can be a memory leak which can in turn lead to other test failures. Safest would be not to run these tests at all, though it would be safer if they were at least run in an isolated process. Though we should also have better facilities built into the test runner for dealing with large memory tests. |
comment:5
~~It seems like there might also be a bug in the doctest parser. It is not handling the
correctly. That's the main reason for the problem...~~ Nevermind, it's just that the behavior here is different on Cygwin than on OSX. On Cygwin the comparison is True, but the |
comment:6
This would be fixed by #25907. |
This is a problem I started getting just since upgrading to 8.3.rc1. Which doesn't make any sense because there were very few changes from 8.3.rc0 where I did not see the issue, and the changes do not seem relevant.
So it's possible the problem was introduced earlier, though I'm still not clear why I never noticed it; I did not have any test failures before.
I need to go back a few versions and see if there is still a problem, then maybe bisect to narrow in on it if the problem goes away on an earlier version. Very strange though.
The problem in the tests starts from
and from there everything else breaks (at least until that test worker crashes).
Component: porting: Cygwin
Issue created by migration from https://trac.sagemath.org/ticket/25884
The text was updated successfully, but these errors were encountered: