DO NOT MERGE, showcase that you can use windows-11-arm64

[seemethere]

[pytorch-bot[bot]]

:link: Helpful Links

:test_tube: See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/vision/8965

• :page_facing_up: Preview Python docs built from this PR

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

:x: 3 New Failures, 12 Unrelated Failures

As of commit aa4af45ac9f71de8bcbdb0303d036c0511119bb3 with merge base 124dfa404f395db90280e6dd84a51c50c742d5fd ():

NEW FAILURES - The following jobs have failed:

• Tests / onnx / linux-job (gh) RuntimeError: Command docker exec -t b046b5c45d8aa3e93020376776e79f4c1552e55e44cc4fd03d28437aa4e98a2d /exec failed with exit code 139
• Tests / unittests-windows (3.10, windows.4xlarge, cpu) / windows-job (gh) Process completed with exit code 139.
• Tests / unittests-windows (3.9, windows.g5.4xlarge.nvidia.gpu, cuda, 11.8) / windows-job (gh) AttributeError: '_OpNamespace' 'image' object has no attribute '_jpeg_version'

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

• Tests / unittests-linux (3.12, linux.12xlarge, cpu) / linux-job (gh) (detected as infra flaky with no log or failing log classifier)
• Tests / unittests-macos (3.12, macos-m1-stable) / macos-job (gh) (similar failure) RuntimeError: Command bash /Users/ec2-user/runner/_work/_temp/exec_script failed with exit code 137
• Tests / unittests-windows (3.12, windows-11-arm64) / windows-job (gh) (matched win rule in flaky-rules.json) Can't find 'action.yml', 'action.yaml' or 'Dockerfile' under 'C:\a\vision\vision\test-infra\.github\actions\teardown-windows'. Did you forget to run actions/checkout before running your local action?

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

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

• Tests / unittests-linux (3.10, linux.12xlarge, cpu) / linux-job (gh) (trunk failure)
• Tests / unittests-linux (3.11, linux.12xlarge, cpu) / linux-job (gh) (trunk failure)
• Tests / unittests-linux (3.9, linux.12xlarge, cpu) / linux-job (gh) (trunk failure)
• Tests / unittests-macos (3.10, macos-m1-stable) / macos-job (gh) (trunk failure) RuntimeError: Command bash /Users/ec2-user/runner/_work/_temp/exec_script failed with exit code 137
• Tests / unittests-macos (3.11, macos-m1-stable) / macos-job (gh) (trunk failure) RuntimeError: Command bash /Users/ec2-user/runner/_work/_temp/exec_script failed with exit code 1
• Tests / unittests-macos (3.9, macos-m1-stable) / macos-job (gh) (trunk failure) RuntimeError: Command bash /Users/ec2-user/runner/_work/_temp/exec_script failed with exit code 137
• Tests / unittests-windows (3.11, windows.4xlarge, cpu) / windows-job (gh) (trunk failure) Process completed with exit code 139.
• Tests / unittests-windows (3.12, windows.4xlarge, cpu) / windows-job (gh) (trunk failure) Process completed with exit code 139.
• Tests / unittests-windows (3.9, windows.4xlarge, cpu) / windows-job (gh) (trunk failure) Process completed with exit code 139.

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