TORCHVISION and TORCH ARM Wheels Date Mismatch

[nWEIdia]

🐛 Describe the bug

During some manual testing we noticed that the nightly today (
pulled in torch dated 20250904 first, but then while installing torchvision 20250904 ARM wheel, it requires 20250903. Because, this torchvision build job got 20250903 pytorch version https://github.com/pytorch/vision/actions/runs/17462534604/job/49590341429#step:15:54

Is this caused by the timing when the binaries would be available? // Is this expected?

cc @ptrblck @tinglvv @atalman @malfet

Versions

20250904 vision nightly.
To reproduce, get an ARM machine and run pip install torchvision --index-url https://download.pytorch.org/whl/nightly

[nWEIdia]

Take python3.10 as example:

1. PyTorch binary uploaded to S3 (download.pytorch.org):
   2025-09-04T13:04:29.9106614Z + aws s3 cp --no-progress --acl public-read /__w/_temp/artifacts/torch-2.9.0.dev20250904+cu130-cp310-cp310-manylinux_2_28_aarch64.whl s3://pytorch/whl/nightly/cu130/ --metadata checksum-sha256=e772a9db42f379d8961d7beca7bd169b8b6bdc8e3c71b32226932596b24b1e8c
   2025-09-04T13:04:37.6558252Z upload: ../../_temp/artifacts/torch-2.9.0.dev20250904+cu130-cp310-cp310-manylinux_2_28_aarch64.whl to s3://pytorch/whl/nightly/cu130/torch-2.9.0.dev20250904+cu130-cp310-cp310-manylinux_2_28_aarch64.whl

2. Vision downloading pytorch

2025-09-04T11:41:31.3818162Z + conda run -p /__w/_temp/conda_environment_17462534604 pip install torch --pre --index-url https://download.pytorch.org/whl/nightly/cu130
2025-09-04T11:42:29.2372997Z WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
2025-09-04T11:42:29.2374481Z
2025-09-04T11:42:29.2374718Z Looking in indexes: https://download.pytorch.org/whl/nightly/cu130
2025-09-04T11:42:29.2375067Z Collecting torch
2025-09-04T11:42:29.2375692Z Downloading https://download.pytorch.org/whl/nightly/cu130/torch-2.9.0.dev20250903%2Bcu130-cp310-cp310-manylinux_2_28_aarch64.whl.metadata (30 kB)

So indeed, they are misaligned by (11:42:29 -> 13:04:37) about 1.5hours.

Might be better if vision aarch64 job could be delayed by e.g. 2 hours.

[atalman]

@nWEIdia This is fixed: https://github.com/pytorch/vision/actions/runs/17673287340/job/50242614112
Multiple failures including pytorch/pytorch#159737

[atalman]

Reopening to look into possibilities of moving bonary workflows about 2 hours later