test_all: skip bisync normalization tests on Dropbox

The bisync normalization test relies on uploading distinct NFC and NFD
versions of the same filename and on the backend supporting in-place
modtime updates. Dropbox normalizes unicode server-side (NFD -> NFC)
and can't set modtime in place, so the test inevitably takes a
different code path on Dropbox and the log diverges from the golden
output without any functional difference.
This commit is contained in:
Nick Craig-Wood
2026-05-07 18:06:54 +01:00
parent f60213545b
commit acb6155654

View File

@@ -158,6 +158,16 @@ backends:
- backend: "dropbox"
remote: "TestDropbox:"
fastlist: false
ignore:
# The bisync normalization test relies on uploading distinct NFC and NFD
# versions of the same filename and on having modtime updates that don't
# require a delete+re-upload. Dropbox normalizes unicode server-side
# (NFD -> NFC) and can't set modtime in place, so the test takes a
# different code path that produces a different log without functional
# difference - the file state ends up correct either way.
- TestBisyncRemoteLocal/normalization
- TestBisyncLocalRemote/normalization
- TestBisyncRemoteRemote/normalization
# - backend: "filefabric"
# remote: "TestFileFabric:"
# fastlist: false