Windows Server 2025 starts allowing some reserved windows file names. Cargo's test suite has a logic that if on Windows it allows aux.rs we don't run a conservative reserved_windows_name test. However it has started failing recently probably due to the windows-latest migration to 2025 on GitHub Actions side, but it doesn't explain why there is still flakiness on 2025 itself.
---- package::reserved_windows_name stdout ----
running `D:\a\cargo\cargo\target\debug\cargo.exe package`
thread 'package::reserved_windows_name' (8372) panicked at tests\testsuite\package.rs:2997:10:
test failed running `D:\a\cargo\cargo\target\debug\cargo.exe package`
error: process exited with code 0 (expected 101)
--- stdout
--- stderr
warning: manifest has no documentation, homepage or repository.
See https://doc.rust-lang.org/cargo/reference/manifest.html#package-metadata for more info.
Packaging foo v0.0.1 (D:\a\cargo\cargo\target\tmp\cit\t2560\foo)
Updating `dummy-registry` index
Packaged 4 files, 1.4KiB (877B compressed)
Verifying foo v0.0.1 (D:\a\cargo\cargo\target\tmp\cit\t2560\foo)
Downloading crates ...
Downloaded bar v1.0.0 (registry `dummy-registry`)
Compiling bar v1.0.0
Compiling foo v0.0.1 (D:\a\cargo\cargo\target\tmp\cit\t2560\foo\target\package\foo-0.0.1)
Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.55s
Problem
Windows Server 2025 starts allowing some reserved windows file names. Cargo's test suite has a logic that if on Windows it allows
aux.rswe don't run a conservativereserved_windows_nametest. However it has started failing recently probably due to thewindows-latestmigration to 2025 on GitHub Actions side, but it doesn't explain why there is still flakiness on 2025 itself.We temporarily skipped this test in #16048.
Observed recently-ish in
And rust-lang/rust:
package::reserved_windows_nametest seems to be flaky rust#147321