cache_lock tests sporadically failing on aarch64 MSVC #16070
Description
We have been seeing some sporadic failures very recently on aarch64 MSVC for the cache_lock tests:
https://github.com/rust-lang/cargo/actions/runs/18222468102/job/51885374574
Tests Windows aarch64 MSVC stable
2025-10-03T12:38:24.5674205Z - Name: Microsoft Windows 11 Desktop by Arm Limited
2025-10-03T12:38:24.5674804Z - Version: 20250917.28.1
---- cache_lock::shared_then_download stdout ----
thread 'cache_lock::shared_then_download' panicked at C:\a\cargo\cargo\crates\cargo-test-support\src\lib.rs:1618:13:
test did not finish within 10 attempts (1.0038996s total)
https://github.com/rust-lang/cargo/actions/runs/18346006177/job/52252773367
Tests Windows aarch64 MSVC stable
2025-10-08T13:18:16.9850971Z - Name: Microsoft Windows 11 Desktop by Arm Limited
2025-10-08T13:18:16.9851599Z - Version: 20250930.30.1
---- cache_lock::mutate_then_download stdout ----
thread 'cache_lock::mutate_then_download' panicked at C:\a\cargo\cargo\crates\cargo-test-support\src\lib.rs:1618:13:
test did not finish within 10 attempts (1.0028045s total)
---- cache_lock::mutate_then_shared stdout ----
thread 'cache_lock::mutate_then_shared' panicked at C:\a\cargo\cargo\crates\cargo-test-support\src\lib.rs:1618:13:
test did not finish within 10 attempts (1.0022253s total)
Unfortunately the partner images do not have release notes, and the documentation at https://github.com/actions/partner-runner-images/blob/main/images/arm-windows-11-image.md is out of date.
The hardware does not look like it has changed recently.
This could likely just be due to more noisy neighbors, though it seems conspicuous that there have been multiple errors in a very short time frame.
The easiest solution may be to just raise the timeout significantly (like 5 seconds instead of 1).