-
Notifications
You must be signed in to change notification settings - Fork 34
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
Theano dot products lead to segfault on Azure pipelines #255
Comments
@twiecki Have you seen this before? It's likely an Azure RAM issue, but I was wondering if you've seen this before. The segfault happens when I try to dot a |
The culprit is the latest release of openblas (0.3.10, July 2020). Reverting to version 0.3.6 fixes this issue (see tests). |
@fbartolic @dfm and anyone else that runs into this: This is a known issue in OpenBLAS: numpy/numpy#16913 The workaround is to
for now if you find that Fore reference, here are the test results with openblas=0.3.6 (passing) and openblas=0.3.10 (failing). |
Revert openblas to 0.3.6 as per #255
I haven't run into this issue lately, and the dev version of the code (on branch https://github.com/rodluger/starry/runs/1953734532?check_suite_focus=true |
This is independent of
starry
but is causing many of the tests (in particularly those that callmap.render()
) to fail.Here is a MWE of a theano operation that segfaults on Azure, and here are the failing test results. The operation is a very simple dot product of two large-ish matrices:
starry/tests/test_segfault.py
Lines 1 to 25 in 160cc49
Did the stack size change on Azure? Are we exceeding the RAM somehow? Looking into this.
The text was updated successfully, but these errors were encountered: