-
Notifications
You must be signed in to change notification settings - Fork 45
linalg.cholesky
not tested for complex dtypes
#228
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
Comments
relevant lines: array-api-tests/array_api_tests/test_linalg.py Lines 126 to 130 in d295a0a
|
Are complex dtypes really skipped for new enough spec levels?
and This me is eyeballing the code though, not sure how to check it. |
Actually, $ git diff
diff --git a/array_api_tests/test_linalg.py b/array_api_tests/test_linalg.py
index 40fe035..5f39da0 100644
--- a/array_api_tests/test_linalg.py
+++ b/array_api_tests/test_linalg.py
@@ -130,6 +130,8 @@ def _test_namedtuple(res, fields, func_name):
def test_cholesky(x, kw):
res = linalg.cholesky(x, **kw)
+ print(f"{x.dtype = }")
+
ph.assert_dtype("cholesky", in_dtype=x.dtype, out_dtype=res.dtype)
ph.assert_result_shape("cholesky", in_shapes=[x.shape],
out_shape=res.shape, expected=x.shape) prints (on several reruns)
|
okay cool, so it seems like Ralf's initial diagnosis was incorrect. I don't know why the linked bug was able to slip through, then. |
I think this is something that I fixed a few months ago. |
As reported in data-apis/array-api-compat#61 (comment),
linalg.cholesky
is only tested on real arrays, hence some bugs slipped through into both array-api-compat and numpy.array_api.The text was updated successfully, but these errors were encountered: