Windows support status: test_index_to_file fails on windows-2022 and windows-11-arm

[yueneiqi]

Summary

Windows CI runs for git-internal are failing on both x86_64 and Arm64 with a panic in internal::index::tests::test_index_to_file.

Environment

• Workflow: integration-test-git-internal.yml (cargo-buckal)
• Targets: x86_64-pc-windows-msvc, aarch64-pc-windows-msvc
• Windows Server 2022 (image windows-2022 20251216.147.1)
• Windows 11 Arm64 (Microsoft Windows 11 Desktop by Arm Limited 20251217.39.1)
• Rust Toolchain: nightly-2025-08-01
• buck2_rev: c6bfcc629378a00921aa04597551442c9e2ea2eb

Failure

Result::unwrap()Err
Test summary: FAILED. 161 passed; 1 failed, exit code 32.

Notes / question

Is Windows (x86_64 and/or Arm64) an officially supported platform for this repo right now?
If yes, what’s the expected fix/workaround for the missing-path error in test_index_to_file?
If no, should we mark Windows CI as allowed to fail or skip this test on Windows?

[genedna]

@yueneiqi ,

I executed all tests with the cargo test --all command on Windows 11 (x86_64), and I can confirm that all cases passed successfully. The internal Git repository utilizes large files in the test cases, so it's likely that the action lacks LFS support.

[yueneiqi]

@yueneiqi ,

I executed all tests with the cargo test --all command on Windows 11 (x86_64), and I can confirm that all cases passed successfully. The internal Git repository utilizes large files in the test cases, so it's likely that the action lacks LFS support.

Got it. Thanks for testing on Windows. I'll try the workflow configuration right away.

[yueneiqi]

The Windows CI passed after I added LFS support. [ci log]

[yueneiqi]

The Windows CI passed after I added LFS support. [ci log]

I mistakenly disabled the tests in the previous CI run. It turns out the error was caused by a missing path on Windows CI, not LFS. [ci log]