Move trunk windows builds to CUDA-12.1 #130446
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/130446
Note: Links to docs will display an error until the docs builds have been completed. ❗ 1 Active SEVsThere are 1 currently active SEVs. If your PR is affected, please view them below: ✅ No FailuresAs of commit 6e4b941 with merge base a205a53 ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
|
@pytorchbot rebase |
|
@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here |
|
Successfully rebased |
pytorchmergebot
force-pushed
the
malfet-patch-1
branch
from
c101a8e to
6e4b941
Compare
|
@pytorchbot merge -f "Lint + win-vs2019-cuda12.1 builds are green" |
Merge startedYour change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Please use Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
That should catch build regressions that were previously only detectable during the nightly builds Win + CUDA-11.8 builds and tests are still run as part of periodic workflow Pull Request resolved: pytorch#130446 Approved by: https://github.com/atalman
Same as : #130446 That should catch build regressions that were previously only detectable during the nightly builds for 12.4 Pull Request resolved: #145844 Approved by: https://github.com/janeyx99, https://github.com/malfet
3 participants
That should catch build regressions that were previously only detectable during the nightly builds
Win + CUDA-11.8 builds and tests are still run as part of periodic workflow