Skip to content

Conversation

@iremyux
Copy link
Collaborator

@iremyux iremyux commented Apr 26, 2023

Draft PR to trigger workflows and get Libtorch artifacts

@pytorch-bot
Copy link

pytorch-bot bot commented Apr 26, 2023

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/100094

Note: Links to docs will display an error until the docs builds have been completed.

❌ 23 New Failures

As of commit d565ffc:

NEW FAILURES - The following jobs have failed:

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@pytorch-bot pytorch-bot bot added the release notes: releng release notes category label Apr 26, 2023
@iremyux iremyux added the ciflow/binaries Trigger all binary build and upload jobs on the PR label Apr 26, 2023
@huydhn
Copy link
Contributor

huydhn commented May 11, 2023

@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.

@iremyux
Copy link
Collaborator Author

iremyux commented May 15, 2023

@huydhn
Thanks a lot for your concern and comments. As a team we are also trying to indorse VS2022 support. That's the reason why I have been working with it instead of VS2019.

@linux-foundation-easycla
Copy link

CLA Missing ID CLA Not Signed

@huydhn
Copy link
Contributor

huydhn commented May 15, 2023

@huydhn Thanks a lot for your concern and comments. As a team we are also trying to indorse VS2022 support. That's the reason why I have been working with it instead of VS2019.

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

@github-actions
Copy link
Contributor

Looks like this PR hasn't been updated in a while so we're going to go ahead and mark this as Stale.
Feel free to remove the Stale label if you feel this was a mistake.
If you are unable to remove the Stale label please contact a maintainer in order to do so.
If you want the bot to never mark this PR stale again, add the no-stale label.
Stale pull requests will automatically be closed after 30 days of inactivity.

@github-actions github-actions bot added the Stale label Jul 15, 2023
@github-actions github-actions bot closed this Aug 14, 2023
@iremyux iremyux deleted the arm64-binaries branch March 21, 2025 13:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ciflow/binaries Trigger all binary build and upload jobs on the PR open source release notes: releng release notes category Stale

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants