-
Notifications
You must be signed in to change notification settings - Fork 27
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
Fixing test on macOS #96
Comments
|
|
We might add some API calls like |
You could maybe just do it in the
They could look like:
and the tests do:
perhaps? |
Thanks for the inputs. I will try to do that. In regards to the MKL version, then 2023 might also be okay - Its only from 2024 and onwards that Intel is stopping the support for macOS? At least it seems like apple is part of the MKL_jll 2023 tag at |
If 2023 works, let's go with that and update the README. |
Hi there,
Thanks for updating the package to run on macOS.
While the code does run, the tests fails on macOS for various reasons. I would like to try to fix that, but I need a few pointers.
For the CI-failures, it might be fixable by pinning to MKL_jll to verison 2022?
In addition the tests fails when MKL is not available locally but Panua-Pardiso is. This is due to MKL being hard-coded into some tests. In the code I see that you simply use
MKL_jll.is_available()
to check if MKL is available. Is it ok to simply add MKL_jll as dependency in the tests?Furthermore the three examples included in the tests hard-codes MKL. This could be fixed by creating three separate examples for Pardiso, but maybe there is a better way?
Cheers,
Mikkel
The text was updated successfully, but these errors were encountered: