[ROCm][CI] Limit caching to ROCm jammy docker images

[jithunnair-amd]

Since the currently intended workflow on the new MI3xx CI capacity is trunk-rocm-mi300.yml, which only needs the jammy images, limiting those to optimize docker caching times.

cc @jeffdaily @sunway513 @pruthvistony @ROCmSupport @dllehr-amd @jataylo @hongxiayang @naromero77amd

[pytorch-bot]

🔗 Helpful Links

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

• 📄 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

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

⏳ 5 Pending, 1 Unrelated Failure

As of commit 2c7d344 with merge base d91269e ():

FLAKY - The following job failed but was likely due to flakiness present on trunk:

• rocm-mi300 / linux-noble-rocm-py3.12-mi300 / test (default, 2, 6, linux.rocm.gpu.gfx942.1) (gh) (similar failure)
  test/cpp_extensions/libtorch_agnostic_2_10_extension/test_version_compatibility.py::FunctionVersionCompatibilityTest::test_mv_tensor_accessor_cuda_works_with_2_9

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

[jithunnair-amd]

@pytorchbot merge -f "Lint is green. No relevant testing in PR runs"

[pytorchmergebot]

Merge started

Your change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Please use -f as last resort and instead consider -i/--ignore-current to continue the merge ignoring current failures. This will allow currently pending tests to finish and report signal before the merge.

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