Rebuild for mkl2024

[regro-cf-autotick-bot]

This PR has been triggered in an effort to update mkl2024.

Notes and instructions for merging this PR:

1. Please merge the PR only after the tests have passed.
2. Feel free to push to the bot's branch to update this PR if needed.

Please note that if you close this PR we presume that the feedstock has been rebuilt, so if you are going to perform the rebuild yourself don't close this PR until the your rebuild has been merged.

---

If this PR was opened in error or needs to be updated please add the bot-rerun label to this PR. The bot will close this PR and schedule another one. If you do not have permissions to add this label, you can use the phrase @conda-forge-admin, please rerun bot in a PR comment to have the conda-forge-admin add it for you.

_{This PR was created by the regro-cf-autotick-bot. The regro-cf-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. Feel free to drop us a line if there are any issues! This PR was generated by https://github.com/regro/cf-scripts/actions/runs/11684729279 - please use this URL for debugging.}

[conda-forge-admin]

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 (recipe/meta.yaml) and found it was in an excellent condition.

[hmaarrfk]

do we want to split up the megabuild and just let things run on the CIs?

its "fun" to manually build things the first 3 times, but I feel like it may be more sustainable if we shed some of our building and uploading responsibilities.

[jeongseok-meta]

I thought the manual build was just a temporary solution for that one Linux CI job, which fails on CI due to insufficient disk space (Quansight/open-gpu-server#47). Once the image has more disk space, we can continue to rely on CI as before?

[hmaarrfk]

I guess how long do you want to wait for that to happen.

[jeongseok-meta]

True.. I'm also okay with trying the split build in parallel. It sounds like the way to go anyway. But I just haven't had time to take a look. If anyone can work on it, that would be great!

[jeongseok-meta]

Btw, I'm currently building for linux, and it might need another 3-5 more hours

[hmaarrfk]

Btw, I'm currently building for linux, and it might need another 3-5 more hours

If you want to keep doing that it is fine.

We might want to add the azure timeouts again to just save CI power

[hmaarrfk]

@conda-forge-admin please rerender

[hmaarrfk]

maybe in version 2.6 we can also just drop 11.8 which would also resolve the disk space issues ...

[jslee02]

Done!

logs: linux_64.zip, linux_aarch64.zip

pkgs:

• https://anaconda.org/jslee02/libtorch
• https://anaconda.org/jslee02/pytorch
• https://anaconda.org/jslee02/pytorch-cpu
• https://anaconda.org/jslee02/pytorch-gpu