Skip to content

Conversation

@h-vetinari
Copy link
Member

Just noticed that we never did the piggyback migrator talked about in #7035 for adding windows support more broadly. We can still do this after this one (and/or wait until our mkl has switched to llvm-openmp).

@h-vetinari h-vetinari requested a review from a team as a code owner May 3, 2025 21:48
@conda-forge-admin
Copy link
Contributor

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
Copy link
Contributor

hmaarrfk commented May 4, 2025

we should wait for the windows builds to get uploaded right?

@h-vetinari
Copy link
Member Author

h-vetinari commented May 4, 2025

Yes... I mean, we could migrate a few feedstocks that don't support windows yet, but some pretty key packages (e.g. torchvision) would be stuck right away.

However, aarch+CUDA also looks like it's failing to upload (no logs visible yet, but already way over average runtime; waiting for the job to finish to see the logs).

In any case, if it's an issue that takes longer to sort out on the anaconda side, it makes no sense to rush IMO.

Xref conda-forge/pytorch-cpu-feedstock#383

@h-vetinari
Copy link
Member Author

For anyone following along, this is blocked on conda/infrastructure#1159

@jeongseok-meta
Copy link

FYI, the windows builds have been uploaded at the 9th attempt: conda-forge/pytorch-cpu-feedstock#383 (comment)

@h-vetinari h-vetinari merged commit 9515b7b into conda-forge:main May 29, 2025
3 checks passed
@h-vetinari h-vetinari deleted the pytorch branch May 29, 2025 23:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants