[CI][CUDA] Move away from cuda12.4, Add cuda12.6 eager CI tests#148602
[CI][CUDA] Move away from cuda12.4, Add cuda12.6 eager CI tests#148602tinglvv wants to merge 6 commits intopytorch:mainfrom
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/148602
Note: Links to docs will display an error until the docs builds have been completed. ❌ 2 New Failures, 14 PendingAs of commit 69d5251 with merge base 98458e5 ( NEW FAILURES - The following jobs have failed:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
|
Thanks Andrey for skipping the test, waiting for the green signal from the test to merge. |
|
If you are modifying slow and periodic workflows, you should tests those as well |
| ;; | ||
| pytorch-linux-jammy-py3.12-triton-cpu) | ||
| CUDA_VERSION=12.4 | ||
| CUDA_VERSION=12.6 |
There was a problem hiding this comment.
This sounds like an oxymoron: why CPU builds needs CUDA (and what this config is for to begin with)
| ;; | ||
| pytorch-linux-jammy-py3.12-halide) | ||
| CUDA_VERSION=12.4 | ||
| CUDA_VERSION=12.6 |
There was a problem hiding this comment.
Halide is part of inductor, so not sure why you are modifying it here.
|
@pytorchbot merge -f "Spartaa aa aa!" |
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 |
#145570
breaking #140793 into eager and inductor benchmarks to unblock
cc @atalman @malfet @nWEIdia @ptrblck