-
Notifications
You must be signed in to change notification settings - Fork 26.3k
[WIP] Draft PR to get Arm64 Libtorch #100094
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
Conversation
|
@iremyux Hi, thank you for working on this change. I want to ask about the use of VS2022 on Windows as I see you try to use that version instead of the default 2019. Is VS2022 an absolute need to build arm64 libtorch on Windows? The reason I'm asking the question is that using pre-installed VS2019 in our Windows AMI gives much better reliability to Windows CI than trying to reinstall a different version of MSVC every time. It's a known issue that reinstalling MSVC on the runner could fail flakily from time to time, i.e. https://github.com/pytorch/pytorch/actions/runs/4951116658/jobs/8857247229. We suspect Windows Defender screwing up the process, but not quite sure. |
|
@huydhn |
|
I see, but please do VS2022 update in a separate PR if it's not needed as part of this change. In fact, you shouldn't install VS at all during CI as it would be done as part of the AMI pytorch/test-infra#1175. The problem is that installing MSVC during CI is very flaky and shouldn't be done at all. You can see that some passes, some fails on your PR https://github.com/pytorch/pytorch/actions/runs/4982100435/jobs/8917275128 |
|
Looks like this PR hasn't been updated in a while so we're going to go ahead and mark this as |
Draft PR to trigger workflows and get Libtorch artifacts