summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2013-08-05 09:47:11 -0700
committerJunio C Hamano <gitster@pobox.com>2013-08-05 09:47:11 -0700
commit0ed45a1cd6571ed89a09791730a9089e932b7c1f (patch)
treea4e0e183bc4d8a3f0040e538f4b5f656ba3a9b69
parent214a5f2e0c86843c5f86494583792cbf3eaf89de (diff)
downloadgit-0ed45a1cd6571ed89a09791730a9089e932b7c1f.tar.gz
t3900: test rejecting log message with NULs correctlydn/test-reject-utf-16
It is not like that our longer term desire is to someday start accept log messages with NULs in them, so it is wrong to mark a test that demonstrates "git commit" that correctly fails given such an input as "expect-failure". "git commit" should fail today, and it should fail the same way in the future given a message with NUL in it. Signed-off-by: Junio C Hamano <gitster@pobox.com>
-rwxr-xr-xt/t3900-i18n-commit.sh4
1 files changed, 2 insertions, 2 deletions
diff --git a/t/t3900-i18n-commit.sh b/t/t3900-i18n-commit.sh
index d48a7c002d..a9e56629d8 100755
--- a/t/t3900-i18n-commit.sh
+++ b/t/t3900-i18n-commit.sh
@@ -34,9 +34,9 @@ test_expect_success 'no encoding header for base case' '
test z = "z$E"
'
-test_expect_failure 'UTF-16 refused because of NULs' '
+test_expect_success 'UTF-16 refused because of NULs' '
echo UTF-16 >F &&
- git commit -a -F "$TEST_DIRECTORY"/t3900/UTF-16.txt
+ test_must_fail git commit -a -F "$TEST_DIRECTORY"/t3900/UTF-16.txt
'