-
-
Notifications
You must be signed in to change notification settings - Fork 35
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
build for MKL 2025.0 #128
base: main
Are you sure you want to change the base?
build for MKL 2025.0 #128
Conversation
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
This runs into problems due to conda-forge/libhwloc-feedstock#83 and (I think) wrong metadata in conda-forge/intel_repack-feedstock#82 (that is, unless MKL now requires 2.28 everywhere) |
@conda-forge-admin rerender |
win64 mkl build is still failing( |
@mkrainiuk could you take a look? |
…onda-forge-pinning 2024.12.17.08.14.21
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( I do have some suggestions for making it better though... For recipe/meta.yaml:
This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12878584559. Examine the logs at this URL for more detail. |
…nda-forge-pinning 2025.01.20.14.49.21
Did some digging where the use of Furthermore, the MKL docs indicate that this should still work. I've asked again in conda-forge/intel_repack-feedstock#83 |
Not having this pushes the solver into weird contortions like
because it ends up prioritizing the newer MKL; apparently despite the
track_features
on the non-default BLAS impl here.We might want to add more track_features here?