[ROCm] enable CI after host upgrades to ROCm 5.3 and ubuntu 22.04

[jeffdaily]

cc @sunway513 @jithunnair-amd @pruthvistony @ROCmSupport

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR
• 📄 Preview C++ docs built from this PR
• ❓ Need help or want to give feedback on the CI? Visit the bot commands wiki or our office hours

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

❗ 1 Active SEVs

There are 1 currently active SEVs. If your PR is affected, please view them below:

• Many CI workflows are failing with KeyError: 'jobs'

❌ 31 Failures

As of commit 59463ea:

NEW FAILURES - The following jobs have failed:

• cuda11.6-py3.10-gcc7-sm86 / test (default, 3, 4, linux.g5.4xlarge.nvidia.gpu)
• cuda11.6-py3.10-gcc7-sm86 / test (default, 4, 4, linux.g5.4xlarge.nvidia.gpu)
• cuda11.6-py3.10-gcc7-sm86 / test (functorch, 1, 1, linux.g5.4xlarge.nvidia.gpu)
• linux-bionic-py3.7-clang9 / test (dynamo, 1, 2, linux.2xlarge)
• linux-bionic-py3.7-clang9 / test (dynamo, 2, 2, linux.2xlarge)
• linux-focal-rocm5.3-py3.8-distributed / test (distributed, 1, 2, linux.rocm.gpu)
• macos-12-py3-arm64 / test (default, 1, 2, macos-m1-12)

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

• cuda11.6-py3.10-gcc7-sm86 / test (default, 1, 4, linux.g5.4xlarge.nvidia.gpu)
• cuda11.6-py3.10-gcc7-sm86 / test (slow, 2, 2, linux.g5.4xlarge.nvidia.gpu)
• ios-12-5-1-x86-64-coreml / build
• linux-bionic-cuda11.6-py3-gcc7-slow-gradcheck / test (default, 1, 2, linux.4xlarge.nvidia.gpu)
• linux-bionic-cuda11.6-py3.10-gcc7 / test (deploy, 1, 1, linux.4xlarge.nvidia.gpu)
• linux-bionic-cuda11.6-py3.9-gcc7 / test (multigpu, 1, 1, linux.16xlarge.nvidia.gpu)
• linux-bionic-cuda11.7-py3.10-gcc7 / test (functorch, 1, 1, linux.4xlarge.nvidia.gpu)
• linux-bionic-cuda11.7-py3.10-gcc7 / test (jit_legacy, 1, 1, linux.4xlarge.nvidia.gpu)
• linux-bionic-cuda11.7-py3.10-gcc7 / test (nogpu_AVX512, 1, 1, linux.2xlarge)
• linux-bionic-cuda11.7-py3.10-gcc7 / test (nogpu_NO_AVX2, 1, 1, linux.2xlarge)
• linux-bionic-py3.7-clang9 / test (functorch, 1, 1, linux.2xlarge)
• linux-focal-py3.7-clang10-onnx / test (default, 1, 2, linux.2xlarge)
• linux-focal-py3.7-clang10-onnx / test (default, 2, 2, linux.2xlarge)
• linux-focal-py3.7-gcc7 / test (backwards_compat, 1, 1, linux.2xlarge)
• linux-focal-py3.7-gcc7 / test (distributed, 2, 2, linux.2xlarge)
• linux-focal-py3.7-gcc7 / test (docs_test, 1, 1, linux.2xlarge)
• linux-focal-py3.7-gcc7 / test (functorch, 1, 1, linux.2xlarge)
• linux-focal-py3.7-gcc7 / test (jit_legacy, 1, 1, linux.2xlarge)
• linux-vulkan-bionic-py3.7-clang9 / test (default, 1, 1, linux.2xlarge)
• macos-12-py3-arm64 / test (default, 2, 2, macos-m1-12)
• macos-12-py3-arm64 / test (functorch, 1, 1, macos-m1-12)
• macos-12-py3-arm64-mps / Run MPS tests
• parallelnative-linux-focal-py3.7-gcc7 / test (default, 1, 2, linux.2xlarge)
• win-vs2019-cpu-py3 / build

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

[jeffdaily]

@pytorchbot merge -f "restore ROCm CI; no other tests affected"

[pytorchmergebot]

Merge started

Your change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes).

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