-
Notifications
You must be signed in to change notification settings - Fork 97
Update VS 2019 and add VS 2022 to Windows AMI #1175
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
@Blackhex is attempting to deploy a commit to the Meta Open Source Team on Vercel. A member of the Team first needs to authorize it. |
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
@seemethere, @izaitsevfb Please advise how to proceed with this PR. Whether it is required that the fix to the VS build tools issue must be released to public, or should I downgrade the VS version to 17.3.6, or can it be merged with the current version of the build tools and updated when the fix will be released? |
This looks ok, however we would need to build the AMI and test it in pytorch-canary before shipping this PR Before building rebase is needed |
@pytorchbot rebase -b main |
fd90dc7
to
e1d4856
Compare
@atalman The branch is rebased but I cannot do the deploy and test it myself. I've build the AMI and deployed it to my own AWS account though. |
ff33a73
to
f446e9d
Compare
@atalman Please advise what should I do more to test and merge this PR. |
Let me setup sometime later today to test this one, building and testing the AMI needs AWS credential from Dev Infra team. I will send you the test PR once I have it |
@huydhn Any update on this? Do you need some assistance/help? |
I was blocked on this because of other recent changes on Windows infra (new AMI, switching runner). Let me pick this up. |
This adds VS 2022 to Windows AMI. The line with https://aka.ms/ link might be reverted once
vs16.11.21_BuildTools.exe
andvs17.4.1_BuildTools.exe
files will be uploaded to https://s3.amazonaws.com/ossci-windows/.Note that there is a fix of thread_local causing fatal error LNK1161: invalid export specification on VS 2022 - Visual Studio Feedback pending, required e.g. for pytorch/pytorch#89511, which will require another VS 2022 version update. Alternatively, the VS 2022 version installed by this change can be downgraded to 16.3.6 which does not suffer this issue.
This is needed to finish pytorch/pytorch#86591