Skip to content
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

[WIP] Force VS2019 as CMake generator #7689

Closed
wants to merge 1 commit into from

Conversation

Blackhex
Copy link
Contributor

Attempt to fix #7682

@pytorch-bot
Copy link

pytorch-bot bot commented Jun 21, 2023

🔗 Helpful Links

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

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

❌ 3 New Failures, 2 Unrelated Failures

As of commit 5852757:

NEW FAILURES - The following jobs have failed:

BROKEN TRUNK - The following jobs failed but were present on the merge base 5178a2e:

👉 Rebase onto the `viable/strict` branch to avoid these failures

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

@Blackhex Blackhex changed the title WIP: Force VS2019 as CMake generator [WIP] Force VS2019 as CMake generator Jun 21, 2023
@Blackhex Blackhex force-pushed the vs2019-vs2022-detection-fix branch 6 times, most recently from 557acac to 70ab84c Compare June 21, 2023 17:59
@Blackhex Blackhex force-pushed the vs2019-vs2022-detection-fix branch from 70ab84c to 5852757 Compare June 21, 2023 18:13
@Blackhex
Copy link
Contributor Author

Not needed at the moment.

@Blackhex Blackhex closed this Jun 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

CMake workflows on Windows are broken
2 participants