Use @release/2.5 instead of @main for CI jobs

[kit1980]

for i in .github/workflows/*.yml; do sed -i -e s#@main#@release/2.5# $i; done

find . | grep .yml | xargs sed -i "s/test-infra-ref: main/test-infra-ref: release\/2.5/g"

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

✅ You can merge normally! (7 Unrelated Failures)

As of commit 9a7e819 with merge base db5f8a0 ():

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

• Tests / unittests-windows (3.12, windows.4xlarge, cpu) / windows-job (gh) (detected as infra flaky with no log or failing log classifier)
• Tests / unittests-windows (3.9, windows.4xlarge, cpu) / windows-job (gh) (detected as infra flaky with no log or failing log classifier)
• Tests / unittests-windows (3.9, windows.g5.4xlarge.nvidia.gpu, cuda, 11.8) / windows-job (gh) (detected as infra flaky with no log or failing log classifier)

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

👉 Rebase onto the `viable/strict` branch to avoid these failures

• Build Windows Conda / pytorch/vision / upload / conda-py3_9-cpu (gh) (trunk failure)
• Build Windows Conda / pytorch/vision / upload / conda-py3_9-cuda11_8 (gh) (trunk failure)
• Build Windows Conda / pytorch/vision / upload / conda-py3_9-cuda12_1 (gh) (trunk failure)
• Build Windows Conda / pytorch/vision / upload / conda-py3_9-cuda12_4 (gh) (trunk failure)

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

[atalman]

lgtm

[github-actions]

Hey @kit1980!

You merged this PR, but no labels were added.
The list of valid labels is available at https://github.com/pytorch/vision/blob/main/.github/process_commit.py