path: root/t/
diff options
authorEric Sunshine <>2018-07-13 05:52:02 (GMT)
committerJunio C Hamano <>2018-07-16 21:55:01 (GMT)
commit079b087c8eaf8119c4b159598e7b6965c1ca3fe9 (patch)
treeb8ee700325bd72dac778dc2ba2f843744def22bf /t/
parentf44a7442f6abeea0059fae46ce482b0c49c27de1 (diff)
t6046/t9833: fix use of "VAR=VAL cmd" with a shell function
Unlike "FOO=bar cmd" one-shot environment variable assignments which exist only for the invocation of 'cmd', those assigned by "FOO=bar shell_func" exist within the running shell and continue to do so until the process exits (or are explicitly unset). It is unlikely that this behavior was intended by the test author. In these particular tests, the "FOO=bar shell_func" invocations are already in subshells, so the assignments don't last too long, don't appear to harm subsequent commands in the same subshells, and don't affect other tests in the same scripts, however, the usage is nevertheless misleading and poor practice, so fix the tests to assign and export the environment variables in the usual fashion. Signed-off-by: Eric Sunshine <> Signed-off-by: Junio C Hamano <>
Diffstat (limited to 't/')
1 files changed, 3 insertions, 1 deletions
diff --git a/t/ b/t/
index fcefffc..38e24f7 100755
--- a/t/
+++ b/t/
@@ -366,7 +366,9 @@ test_expect_success '2c-check: Modify b & add c VS rename b->c' '
git checkout A^0 &&
- GIT_MERGE_VERBOSITY=3 test_must_fail git merge -s recursive B^0 >out 2>err &&
+ test_must_fail git merge -s recursive B^0 >out 2>err &&
test_i18ngrep "CONFLICT (rename/add): Rename b->c" out &&
test_i18ngrep ! "Skipped c" out &&