[ROCm] upgrade ROCm CI builds to py3.10#134108
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/134108
Note: Links to docs will display an error until the docs builds have been completed. ❌ 2 New Failures, 3 Unrelated FailuresAs of commit 9e85c89 with merge base c64ae60 ( NEW FAILURES - The following jobs have failed:
FLAKY - The following jobs failed but were likely due to flakiness present on trunk:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
|
I don't believe any of these failures are new and the b2b-gemm tests are passing: |
|
@pytorchbot rebase |
|
@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here |
|
Successfully rebased |
d24c4dd to
0c28943
Compare
|
@malfet could you take a look at this. Should resolve these b2b-gemm issues we pointed out related to py3.8 ROCm failures are expected, and the timeout is due to keep-going enable with the current test_transformers failures. |
|
Waiting for this PR #132895 to merge before this PR. |
|
@pytorchbot rebase |
|
@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here |
|
Successfully rebased |
0c28943 to
6a0bdb7
Compare
|
@pytorchbot rebase |
|
@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here |
|
Rebase failed due to Command Raised by https://github.com/pytorch/pytorch/actions/runs/10833692309 |
196041b to
6988702
Compare
|
@pytorchbot rebase |
|
@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here |
|
Successfully rebased |
6988702 to
9e85c89
Compare
|
Failures seem unrelated. Opening for review |
|
cc: @malfet |
atalman
left a comment
There was a problem hiding this comment.
lgtm. Please followup on periodic / linux-focal-rocm6.1-py3.10 / test (distributed, 3, 3, linux.rocm.gpu)
@atalman Yes, we're looking into the timeouts seen in the distributed job. However, it is not an issue related to the python version, so it shouldn't be a blocker for this PR. |
|
@pytorchbot merge -f "CI failures are unrelated to py3.10 upgrade" |
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 |
Upgrade ROCm CI builds to py3.10 Pull Request resolved: pytorch#134108 Approved by: https://github.com/jeffdaily, https://github.com/jithunnair-amd, https://github.com/atalman
|
@pytorchmergebot cherry-pick --onto release/2.5 -c critical |
Cherry picking #134108Command Details for Dev Infra teamRaised by workflow job |
Upgrade ROCm CI builds to py3.10 Pull Request resolved: #134108 Approved by: https://github.com/jeffdaily, https://github.com/jithunnair-amd, https://github.com/atalman Co-authored-by: Jack Taylor <jack.taylor@amd.com>
Upgrade ROCm CI builds to py3.10
cc @jeffdaily @sunway513 @jithunnair-amd @pruthvistony @ROCmSupport @dllehr-amd @hongxiayang