-
Notifications
You must be signed in to change notification settings - Fork 22
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
2 NumPy/MKL issues on CPU with tests/test_linalg.py::test_eig_arange #1005
Labels
bug
Something isn't working
Comments
densmirn
changed the title
[numpy/mkl] tests/test_linalg.py::test_eig_arange raises 2 issues on CPU
2 NumPy/MKL issues on CPU with tests/test_linalg.py::test_eig_arange
Oct 14, 2021
6 tasks
I tested this old bug with the new MKL package available on the public channel and did not find any problems described in this issue.
conda list
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Test
tests/test_linalg.py::test_eig_arange
raises 2 issues on CPU.const std::int64_t scratchpad_size = mkl_lapack::syevd_scratchpad_size<double>(DPNP_QUEUE, oneapi::mkl::job::vec, oneapi::mkl::uplo::upper, size, lda);
in the functiondpnp_eigvals_c
returns wrong value that causesout of memory
issue.oneapi::mkl::lapack::syevd
indpnp_eigvals_c
causes segfault.Example of the command to reproduce the issues:
SYCL_DEVICE_FILTER=cpu pytest tests/test_linalg.py::test_eig_arange[2-float64]
High-level reason of the issues is
numpy
is imported beforedpnp
in third party tests. E.g. change #1004 gets around the issue.Low-level reason of the issues could be related to MKL runtime library loaded during numpy import that needs to be investigated.
DPNP was built from source on commit 61ae592 with below environment:
The text was updated successfully, but these errors were encountered: