From: Junio C Hamano <gitster@pobox.com>
To: Elijah Newren <newren@gmail.com>
Cc: git@vger.kernel.org, corrmage@gmail.com, avarab@gmail.com,
Johannes.Schindelin@gmx.de, sbeller@google.com
Subject: Re: [PATCH 1/3] t3401: add another directory rename testcase for rebase and am
Date: Wed, 29 Aug 2018 15:12:27 -0700 [thread overview]
Message-ID: <xmqqo9dkakl0.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <20180829070613.11793-2-newren@gmail.com> (Elijah Newren's message of "Wed, 29 Aug 2018 00:06:11 -0700")
Elijah Newren <newren@gmail.com> writes:
> +test_expect_success 'rebase --interactive: NO directory rename' '
> + test_when_finished "git -C no-dir-rename rebase --abort" &&
> + (
> + cd no-dir-rename &&
> +
> + git checkout B^0 &&
> +
> + set_fake_editor &&
> + FAKE_LINES="1" test_must_fail git rebase --interactive A &&
Is this a single-shot environment assignment? That would have been
caught with the test linter.
Perhaps squshing this in would be sufficient fix?
t/t3401-rebase-and-am-rename.sh | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/t/t3401-rebase-and-am-rename.sh b/t/t3401-rebase-and-am-rename.sh
index 94bdfbd69c..13e09afec0 100755
--- a/t/t3401-rebase-and-am-rename.sh
+++ b/t/t3401-rebase-and-am-rename.sh
@@ -141,7 +141,7 @@ test_expect_success 'rebase --interactive: NO directory rename' '
git checkout B^0 &&
set_fake_editor &&
- FAKE_LINES="1" test_must_fail git rebase --interactive A &&
+ test_must_fail env FAKE_LINES="1" git rebase --interactive A &&
git ls-files -s >out &&
test_line_count = 6 out &&
@@ -160,7 +160,7 @@ test_expect_success 'rebase (am): NO directory rename' '
git checkout B^0 &&
set_fake_editor &&
- FAKE_LINES="1" test_must_fail git rebase A &&
+ test_must_fail env FAKE_LINES="1" git rebase A &&
git ls-files -s >out &&
test_line_count = 6 out &&
@@ -179,7 +179,7 @@ test_expect_success 'rebase --merge: NO directory rename' '
git checkout B^0 &&
set_fake_editor &&
- FAKE_LINES="1" test_must_fail git rebase --merge A &&
+ test_must_fail env FAKE_LINES="1" git rebase --merge A &&
git ls-files -s >out &&
test_line_count = 6 out &&
next prev parent reply other threads:[~2018-08-29 22:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-28 12:27 A rebase regression in Git 2.18.0 Nikolay Kasyanov
2018-08-28 13:17 ` Ævar Arnfjörð Bjarmason
2018-08-28 13:33 ` Johannes Schindelin
2018-08-28 13:46 ` Nikolay Kasyanov
2018-08-28 15:35 ` Elijah Newren
2018-08-28 16:58 ` Junio C Hamano
2018-08-29 7:06 ` [PATCH 0/3] Turn off directory rename detection in am -3 Elijah Newren
2018-08-29 7:06 ` [PATCH 1/3] t3401: add another directory rename testcase for rebase and am Elijah Newren
2018-08-29 22:12 ` Junio C Hamano [this message]
2018-08-29 23:47 ` Elijah Newren
2018-08-30 16:01 ` Junio C Hamano
2018-08-30 16:26 ` Elijah Newren
2018-08-29 7:06 ` [PATCH 2/3] merge-recursive: add ability to turn off directory rename detection Elijah Newren
2018-08-29 12:54 ` Johannes Schindelin
2018-08-29 23:00 ` Elijah Newren
2018-08-29 7:06 ` [PATCH 3/3] am: avoid directory rename detection when calling recursive merge machinery Elijah Newren
2018-08-29 12:51 ` Johannes Schindelin
2018-08-30 16:41 ` A rebase regression in Git 2.18.0 Elijah Newren
2018-08-31 10:11 ` Johannes Schindelin
2018-08-31 19:37 ` Elijah Newren
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqo9dkakl0.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=avarab@gmail.com \
--cc=corrmage@gmail.com \
--cc=git@vger.kernel.org \
--cc=newren@gmail.com \
--cc=sbeller@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).