Rename remaining periodic and xpu workflows py3.9->py3.10

[atalman]

Fix naming py3.9 should be py 3.10
These jobs where already migrated to 3.10
Please see: https://github.com/pytorch/pytorch/actions/runs/18091356163/job/51472526131#step:16:224

Python version:
+ python --version
Python 3.10.18

[pytorch-bot]

🔗 Helpful Links

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

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

❌ 11 New Failures, 7 Unrelated Failures

As of commit 293a2b9 with merge base d633bac ():

NEW FAILURES - The following jobs have failed:

• periodic / linux-jammy-cuda12.8-py3-gcc11-slow-gradcheck / test (default, 1, 8, lf.linux.g5.4xlarge.nvidia.gpu, module:slowgradcheck) (gh)
  inductor/test_cuda_select_algorithm.py::TestSelectAlgorithmCudaCUDA::test_int8_woq_mm_concat_cuda_batch_size_1_mid_dim_1_in_features_128_out_features_64_cuda_bfloat16
• periodic / linux-jammy-cuda12.8-py3-gcc11-slow-gradcheck / test (default, 7, 8, lf.linux.g5.4xlarge.nvidia.gpu, module:slowgradcheck) (gh)
  inductor/test_cuda_select_algorithm.py::TestSelectAlgorithmCudaCUDA::test_int8_woq_mm_concat_cuda_batch_size_32_mid_dim_1_in_features_128_out_features_64_cuda_bfloat16
• periodic / linux-jammy-cuda12.8-py3.10-gcc9-debug / test (default, 2, 7, lf.linux.4xlarge.nvidia.gpu, oncall:debug-build) (gh)
  inductor/test_cuda_select_algorithm.py::TestSelectAlgorithmCudaCUDA::test_int8_woq_mm_concat_cuda_batch_size_1_mid_dim_1_in_features_128_out_features_64_cuda_bfloat16
• periodic / linux-jammy-cuda12.8-py3.10-gcc9-debug / test (default, 3, 7, lf.linux.4xlarge.nvidia.gpu, oncall:debug-build) (gh)
  inductor/test_cuda_select_algorithm.py::TestSelectAlgorithmCudaCUDA::test_int8_woq_mm_concat_cuda_batch_size_32_mid_dim_8_in_features_128_out_features_64_cuda_bfloat16
• periodic / linux-jammy-cuda12.8-py3.10-gcc9-debug / test (default, 4, 7, lf.linux.4xlarge.nvidia.gpu, oncall:debug-build) (gh)
  inductor/test_cuda_select_algorithm.py::TestSelectAlgorithmCudaCUDA::test_int8_woq_mm_cuda_batch_size_1_mid_dim_1_in_features_144_out_features_64_cuda_bfloat16
• periodic / linux-jammy-cuda12.8-py3.10-gcc9-debug / test (default, 6, 7, lf.linux.4xlarge.nvidia.gpu, oncall:debug-build) (gh)
  RuntimeError: export/test_serialize 1/1 failed!
• periodic / linux-jammy-cuda12.8-py3.10-gcc9-debug / test (default, 7, 7, lf.linux.4xlarge.nvidia.gpu, oncall:debug-build) (gh)
  test_cuda.py::TestCuda::test_fast_index_overflow
• s390x-periodic / linux-manylinux-2_28-py3-cpu-s390x / test (default, 1, 10, linux.s390x) (gh)
  'test/test_tensor_creation_ops.py::TestTensorCreationCPU::test_cat_large_tensor_cpu_float32'
• s390x-periodic / linux-manylinux-2_28-py3-cpu-s390x / test (default, 5, 10, linux.s390x) (gh)
  test_nestedtensor.py::TestNestedTensorSubclassCPU::test_as_nested_tensor_from_tensor_dim_2_layout_jagged_requires_grad_False_contiguous_False_cpu_float16
• s390x-periodic / linux-manylinux-2_28-py3-cpu-s390x / test (default, 7, 10, linux.s390x) (gh)
  test_nestedtensor.py::TestNestedTensorSubclassCPU::test_as_nested_tensor_from_tensor_dim_2_layout_jagged_requires_grad_False_contiguous_False_cpu_float64
• xpu / linux-jammy-xpu-n-py3.10 / test (default, 8, 8, linux.idc.xpu) (gh)
  inductor/test_aot_inductor.py::AOTInductorTestABICompatibleGpu::test_aoti_user_defined_triton_kernel_profiling_xpu

FLAKY - The following jobs failed but were likely due to flakiness present on trunk:

• periodic / linux-jammy-cuda12.8-py3-gcc11-slow-gradcheck / test (default, 4, 8, lf.linux.g5.4xlarge.nvidia.gpu, module:slowgradcheck) (gh) (similar failure)
  inductor/test_multi_kernel.py::MultiKernelTest::test_triton_relu_fused_gemm
• xpu / linux-jammy-xpu-n-py3.10 / test (default, 7, 8, linux.idc.xpu) (gh) (similar failure)
  'Test'

UNSTABLE - The following jobs are marked as unstable, possibly due to flakiness on trunk:

• periodic / linux-jammy-cuda12.4-py3.10-gcc11 / test (legacy_nvidia_driver, 1, 5, lf.linux.4xlarge.nvidia.gpu, unstable) (gh) (#163657)
  The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
• periodic / linux-jammy-cuda12.4-py3.10-gcc11 / test (legacy_nvidia_driver, 2, 5, lf.linux.4xlarge.nvidia.gpu, unstable) (gh) (#163657)
  The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
• periodic / linux-jammy-cuda12.4-py3.10-gcc11 / test (legacy_nvidia_driver, 3, 5, lf.linux.4xlarge.nvidia.gpu, unstable) (gh) (#163657)
  The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
• periodic / linux-jammy-cuda12.4-py3.10-gcc11 / test (legacy_nvidia_driver, 4, 5, lf.linux.4xlarge.nvidia.gpu, unstable) (gh) (#163657)
  The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
• periodic / linux-jammy-cuda12.4-py3.10-gcc11 / test (legacy_nvidia_driver, 5, 5, lf.linux.4xlarge.nvidia.gpu, unstable) (gh) (#163657)
  The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.

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

[atalman]

@pytorchmergebot merge -f "the failures are not related"

[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