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
Intermittent "Fatal Python error: Cannot recover from stack overflow." from wester tests on Travis #11274
Comments
I haven't been able to reproduce this locally, even with the same PYTHONHASHSEED and so on. It may be Linux only (I only tested on OS X). |
Is is possible to find out how much memory is allocated for the virtual machines running the Travis jobs? |
I don't see any information about that in the logs. If there is a Linux command that shows the total memory, you can create .travis.yml that runs that command and look at the output. |
This would probably suffice:
|
Would also be useful to run the tests with By the way, this error has happened before, which ended up being a bug in Python. |
I'm beginning to suspect that this is caused by a bug in SymPy. The failing test is (most probably) |
There is indeed a RecursionError in SymPy, but the issue is that this shouldn't crash Python. It should be caught by the interpreter. Likely the test that is causing this is an XFAIL test. |
This is the same thing that happened with the aforementioned CPython bug 14537. A recursion error in an XFAIL test triggered a "Python error: Cannot recover from stack overflow." |
There is |
The example above is in 3.3.5. But I also saw it in a 3.5 build (I'm not able to find it, though. People have a tendency to just restart builds when they fail, so intermittent failures like this one go unfixed for a long time.) |
I have modified the meijerint lookup table in #11283 so that the |
Haven't seen this in a while. I'm assuming it was fixed. |
For example, at https://travis-ci.org/sympy/sympy/jobs/136763509. I've also seen it in Python 3.5.
The text was updated successfully, but these errors were encountered: