-
Notifications
You must be signed in to change notification settings - Fork 79
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
ci: add pyodide build #995
Conversation
5b099df
to
3c05e97
Compare
Signed-off-by: Henry Schreiner <henryschreineriii@gmail.com>
3c05e97
to
65ac58e
Compare
This is the only failing part, don't know if it's directly pyodide's fault:
|
The two errors seem related to m = np.atleast_2d(m)
if np.all(m.T == m):
# maybe check this first https://en.wikipedia.org/wiki/Diagonally_dominant_matrix
# and only try cholesky if that fails
try:
np.linalg.cholesky(m)
except np.linalg.LinAlgError:
return False
return True
return False This returns true in those failing cases although it should return false. Apparently, |
Perhaps the line |
I bet NumPy is compiled with exceptions turned off; maybe this function actually raises the exception from the compiled code? I'll look into this and report to pyodide with what I find. The snippet above is extremely helpful, thank you! |
@henryiii I made a patch which may work around the failing test in pyodide, but I cannot test it because the pyodide build now fails because of some build-system issue. I am closing this PR now, you can reopen it when you find the time to finish this. |
Testing this.