KEMBAR78
Cleanup VS 2019 refs in pytorch by Camyll · Pull Request #145863 · pytorch/pytorch · GitHub
Skip to content

Conversation

@Camyll
Copy link
Contributor

@Camyll Camyll commented Jan 28, 2025

Related to: #128835
Follow up on PR: #145319

@Camyll Camyll requested a review from a team as a code owner January 28, 2025 19:26
@pytorch-bot
Copy link

pytorch-bot bot commented Jan 28, 2025

🔗 Helpful Links

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

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

✅ No Failures

As of commit b57b38b with merge base 99dd846 (image):
💚 Looks good so far! There are no failures yet. 💚

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 Jan 28, 2025
@Skylion007 Skylion007 added the ciflow/binaries Trigger all binary build and upload jobs on the PR label Jan 28, 2025
export VC_YEAR=2022

if [[ "$DESIRED_CUDA" == 'xpu' ]]; then
export VC_YEAR=2022
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: You could also remove this line

@huydhn
Copy link
Contributor

huydhn commented Jan 28, 2025

Searching for vs2019 and there are some additional files / references we can remove I think https://github.com/search?q=repo%3Apytorch%2Fpytorch%20vs2019&type=code

Copy link
Contributor

@malfet malfet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If it works, then sure...

secrets: inherit

win-vs2019-cpu-py3-build:
win-vs2022-cpu-py3-build:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Alas, this is a no-op, as VC version is defined by AMI

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, we are going to clean up the AMI next

@cyyever cyyever changed the title Cleanup VS 2019 refs in pytorch pytorch Cleanup VS 2019 refs in pytorch Jan 29, 2025
@Camyll
Copy link
Contributor Author

Camyll commented Feb 6, 2025

@pytorchbot merge

@pytorch-bot pytorch-bot bot added the ciflow/trunk Trigger trunk jobs on your pull request label Feb 6, 2025
@pytorchmergebot
Copy link
Collaborator

Merge started

Your change will be merged once all checks pass (ETA 0-4 Hours).

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Advanced Debugging
Check the merge workflow status
here

@pytorchmergebot
Copy link
Collaborator

Merge failed

Reason: 2 mandatory check(s) failed. The first few are:

Dig deeper by viewing the failures on hud

Details for Dev Infra team Raised by workflow job

Failing merge rule: Core Maintainers

@Camyll
Copy link
Contributor Author

Camyll commented Feb 7, 2025

@pytorchbot merge

@pytorchmergebot
Copy link
Collaborator

Merge started

Your change will be merged once all checks pass (ETA 0-4 Hours).

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Advanced Debugging
Check the merge workflow status
here

@pytorchmergebot
Copy link
Collaborator

Merge failed

Reason: 1 jobs have failed, first few of them are: linux-binary-manywheel / manywheel-py3_12-rocm6_3-build / build

Details for Dev Infra team Raised by workflow job

@huydhn
Copy link
Contributor

huydhn commented Feb 10, 2025

@pytorchbot merge

@pytorchmergebot
Copy link
Collaborator

Merge started

Your change will be merged once all checks pass (ETA 0-4 Hours).

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Advanced Debugging
Check the merge workflow status
here

test-matrix: ${{ needs.macos-py3-arm64-build.outputs.test-matrix }}
secrets: inherit

win-vs2019-cpu-py3-build:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this mean that we're not testing windows at all anymore?

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've same concern here, I didn't see any replacement for PR tests on Windows, it is just removed.
Will you add it in a separate PR?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oops, I don't think this was in the original PR before. @Camyll Could you submit a PR to revert the last commit you have b57b38b and put these jobs back? You want to rename them from vs2019 to vs2022 instead

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@github-actions github-actions bot deleted the cleanup_vs_2019 branch March 14, 2025 02:08
xuhancn added a commit to xuhancn/pytorch that referenced this pull request May 1, 2025
xuhancn added a commit to xuhancn/pytorch that referenced this pull request May 1, 2025
xuhancn added a commit to xuhancn/pytorch that referenced this pull request May 10, 2025
pytorchmergebot pushed a commit that referenced this pull request May 10, 2025
xuhancn added a commit to xuhancn/pytorch that referenced this pull request May 12, 2025
atalman pushed a commit that referenced this pull request May 14, 2025
atalman added a commit to atalman/pytorch that referenced this pull request Jun 9, 2025
pytorchmergebot pushed a commit that referenced this pull request Jun 10, 2025
This reverts commit e4f2282.
I believe fix PR was landed #153480 that triggered the revert.
Hence this is reland.

Pull Request resolved: #155478
Approved by: https://github.com/malfet
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 ciflow/trunk Trigger trunk jobs on your pull request Merged release notes: releng release notes category test-config/default

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants