The request is not supported

Locally, and on windows-2025 (1.23 and 1.24), the TestCopyRange test is failing with The request is not supported.

run tests on all windows runners · rasa/syncthing@aedaa78 · GitHub shows:

=== RUN   TestCopyRange
=== RUN   TestCopyRange/tmp
=== RUN   TestCopyRange/tmp/duplicate_extents
=== RUN   TestCopyRange/tmp/duplicate_extents/append_to_end
    filesystem_copy_range_test.go:339: The request is not supported.
--- FAIL: TestCopyRange/tmp/duplicate_extents/append_to_end (0.02s)
=== RUN   TestCopyRange/tmp/duplicate_extents/append_to_end_offsets_at_start
    filesystem_copy_range_test.go:339: The request is not supported.
--- FAIL: TestCopyRange/tmp/duplicate_extents/append_to_end_offsets_at_start (0.02s)
=== RUN   TestCopyRange/tmp/duplicate_extents/overwrite_part_of_destination_region
    filesystem_copy_range_test.go:339: The request is not supported.
--- FAIL: TestCopyRange/tmp/duplicate_extents/overwrite_part_of_destination_region (0.02s)
=== RUN   TestCopyRange/tmp/duplicate_extents/overwrite_all_of_destination
    filesystem_copy_range_test.go:339: The request is not supported.
--- FAIL: TestCopyRange/tmp/duplicate_extents/overwrite_all_of_destination (0.02s)
=== RUN   TestCopyRange/tmp/duplicate_extents/overwrite_part_of_destination
    filesystem_copy_range_test.go:339: The request is not supported.
--- FAIL: TestCopyRange/tmp/duplicate_extents/overwrite_part_of_destination (0.02s)
=== RUN   TestCopyRange/tmp/duplicate_extents/destination_gets_expanded_as_it_is_being_written_to
    filesystem_copy_range_test.go:339: The request is not supported.

What is windows 2025?

The tests assume certain filesystem semantics on windows, perhaps the filesystem you are on (or the os) does not support it, hence failures are expected.

On Windows, this works only on specific filesystems (other than NTFS), so the use case is extremely niche. I think I did the test on ReFS under Windows Server when the feature was first being implemented to check if it actually functions as intended.

See https://docs.syncthing.net/advanced/folder-copyrangemethod.

Sorry if I wasn’t clear, windows-2025 is the latest GitHub runner (though windows-latest refers to the windows-2022 runner). The test also fails locally on Windows 11.

This test does not fail on NTFS on either the windows-latest or the windows-2019 runners, so something changed. So, either Windows 11/windows-2025 now require an ReFS filesystem, a different error is now being returned, or support was dropped.

If given the go ahead, I can craft a PR thats runs the test on a ReFS-formatted .VHDX, to see if that fixes it.

I fixed this in a one-line PR in fix(tests): fix error check on Windows 2025 (fixes #10164) by rasa · Pull Request #10165 · syncthing/syncthing · GitHub

2 Likes