path: root/t/
diff options
authorAlexandr Miloslavskiy <>2019-09-24 10:40:29 (GMT)
committerJunio C Hamano <>2019-09-28 04:49:47 (GMT)
commit0b63fd6965350fd0159f7712b3582ba83cbfca25 (patch)
treebffffaf720fb7fd834b5d825d1bfbedd8af978da /t/
parent5fa0f5238b0cd46cfe7f6fa76c3f526ea98148d9 (diff)
t0028: fix test for UTF-16-LE-BOM
According to its name, the test is designed for UTF-16-LE-BOM. However, possibly due to copy&paste oversight, it was using UTF-32. While the test succeeds (extra \000\000 are interpreted as NUL), I myself had an unrelated problem which caused the test to fail. When analyzing the failure I was quite puzzled by the fact that the test is obviously buggy. And it seems that I'm not alone: Fix the test to follow its original intention. Signed-off-by: Alexandr Miloslavskiy <> Reviewed-by: Torsten Bögershausen <> Signed-off-by: Junio C Hamano <>
Diffstat (limited to 't/')
1 files changed, 1 insertions, 1 deletions
diff --git a/t/ b/t/
index 1090e65..5493cf3 100755
--- a/t/
+++ b/t/
@@ -40,7 +40,7 @@ test_expect_success 'setup test files' '
printf "$text" | write_utf16 >test.utf16.raw &&
printf "$text" | write_utf32 >test.utf32.raw &&
printf "\377\376" >test.utf16lebom.raw &&
- printf "$text" | iconv -f UTF-8 -t UTF-32LE >>test.utf16lebom.raw &&
+ printf "$text" | iconv -f UTF-8 -t UTF-16LE >>test.utf16lebom.raw &&
# Line ending tests
printf "one\ntwo\nthree\n" >lf.utf8.raw &&