git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH] Show a failure of rebase -p if the merge had a conflict

From
Johannes Sixt <j6t@kdbg.org>
Date
Dec 11, 2008, 16:21 UTC
Message-ID
<1229012461-31377-1-git-send-email-j6t@kdbg.org>

This extends t3409-rebase-preserve-merges by a case where the merge that is rebased has a conflict. Therefore, the rebase stops and expects that the user resolves the conflict. However, currently rebase --continue fails because .git/rebase-merge/author-script is missing.

The test script had allocated two identical clones, but only one of them (clone2) was used. Now we use both as indicated in the comment. Also, an instance of && was missing in the setup part.

Signed-off-by: Johannes Sixt <j6t@kdbg.org>
---
  BTW, I'm not 100% sure whether the additional tests of what to expect
  from the test if it did not fail are correct.
  I am unable to fix the failure.
  -- Hannes
  [Sorry, Junio, for the resend. git send-email & PEBCAK. :-/ ]
 t/t3409-rebase-preserve-merges.sh |   43 ++++++++++++++++++++++++++++++++----
 1 files changed, 38 insertions(+), 5 deletions(-)
diff --git a/t/t3409-rebase-preserve-merges.sh b/t/t3409-rebase-preserve-merges.sh
index 8cde40f..02a6401 100755
--- a/t/t3409-rebase-preserve-merges.sh
+++ b/t/t3409-rebase-preserve-merges.sh
@@ -11,7 +11,7 @@ Run "git rebase -p" and check that merges are properly carried along
 GIT_AUTHOR_EMAIL=bogus_email_address
 export GIT_AUTHOR_EMAIL
 
-#echo 'Setting up:
+#Clone 1 (trivial merge):
 #
 #A1--A2  <-- origin/master
 # \   \
@@ -19,7 +19,15 @@ export GIT_AUTHOR_EMAIL
 #   \
 #    B2  <-- origin/topic
 #
-#'
+#Clone 2 (conflicting merge):
+#
+#A1--A2--B3   <-- origin/master
+# \       \
+#  B1------M  <-- topic
+#   \
+#    B2       <-- origin/topic
+#
+# In both cases, 'topic' is rebased onto 'origin/topic'.
 
 test_expect_success 'setup for merge-preserving rebase' \
 	'echo First > A &&
@@ -37,12 +45,19 @@ test_expect_success 'setup for merge-preserving rebase' \
 	cd clone1 &&
 	git checkout -b topic origin/topic &&
 	git merge origin/master &&
-	cd ..
+	cd .. &&
+
+	echo Fifth > B &&
+	git add B &&
+	git commit -m "Add different B" &&
 
 	git clone ./. clone2
 	cd clone2 &&
 	git checkout -b topic origin/topic &&
-	git merge origin/master &&
+	test_must_fail git merge origin/master &&
+	echo Resolved > B &&
+	git add B &&
+	git commit -m "Merge origin/master into topic" &&
 	cd .. &&
 
 	git checkout topic &&
@@ -51,11 +66,29 @@ test_expect_success 'setup for merge-preserving rebase' \
 '
 
 test_expect_success 'rebase -p fakes interactive rebase' '
-	cd clone2 &&
+	(
+	cd clone1 &&
 	git fetch &&
 	git rebase -p origin/topic &&
 	test 1 = $(git rev-list --all --pretty=oneline | grep "Modify A" | wc -l) &&
 	test 1 = $(git rev-list --all --pretty=oneline | grep "Merge commit" | wc -l)
+	)
+'
+
+test_expect_failure '--continue works after a conflict' '
+	(
+	cd clone2 &&
+	git fetch &&
+	test_must_fail git rebase -p origin/topic &&
+	test 2 = $(git ls-files B | wc -l) &&
+	echo Resolved again > B &&
+	test_must_fail git rebase --continue &&
+	git add B &&
+	git rebase --continue &&
+	test 1 = $(git rev-list --all --pretty=oneline | grep "Modify A" | wc -l) &&
+	test 1 = $(git rev-list --all --pretty=oneline | grep "Add different" | wc -l) &&
+	test 1 = $(git rev-list --all --pretty=oneline | grep "Merge origin" | wc -l)
+	)
 '
 
 test_done
-- 
1.6.1.rc2.22.gf3bf84
Next: Johannes Sixt
Message 1 of 6 in “Show a failure of rebase -p if the merge had a conflict”
  1. Show a failure of rebase -p if the merge had a conflictJohannes Sixt, Dec 11, 2008
  2. 1/2 Show a failure of rebase -p if the merge had a conflictJohannes Sixt, Dec 15, 2008
  3. 2/2 rebase -i -p: Fix --continue after a merge could not be redoneJohannes Sixt, Dec 15, 2008
  4. Junio C HamanoDec 15, 2008
  5. Johannes SchindelinDec 22, 2008
  6. Johannes SchindelinDec 22, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.