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

[PATCH] Add test that checks diverse aspects of updating remote and tracking branches

From
Alex Riesen <raa.lkml@gmail.com>
Date
Nov 15, 2007, 20:46 UTC
Message-ID
<20071115204611.GB3552@steel.home>
In-Reply-To
<20071115042625.GA10094@sigill.intra.peff.net>

Because we haven't settled on what the exit status from "git push" command itself should be in such a partial failure case, do not check the exit status from it for now.

Signed-off-by: Alex Riesen <raa.lkml@gmail.com>
---
Jeff King, Thu, Nov 15, 2007 05:26:26 +0100:
Show 16 quoted lines
> On Tue, Nov 13, 2007 at 06:10:48PM -0500, Jeff King wrote:
> 
> > > This one is on top of what is in next. It also include the check for
> > > deleting remote braches I sent before. Regarding this one: if a remote
> > > branch is deleted, shouldn't the matching tracking branch be removed
> > > as well? The code in master seem to do that.
> > 
> > Yes, it should (the code in update_tracking_ref seems to handle that
> > case, but I haven't tested, so I may have bungled something). I am
> > literally walking out the door, now, though, so I will be out of touch
> > for at least a day.
> 
> After I became disconnected, I looked at my 'next', and the reason for
> the failure to delete the ref seems to be your is_null_sha1
> error-checking patch, which Junio put in next. But maybe you have
> figured that out in the intervening time. :)

I didn't. But Junio already has all your patches in pu, so I activated the deletion test and rebased it on top of your patches in his tree (jk/send-pack, according to merge commit). Tried: works.

 t/t5404-tracking-branches.sh |   28 +++++++++++++++++++++++++---
 1 files changed, 25 insertions(+), 3 deletions(-)
diff --git a/t/t5404-tracking-branches.sh b/t/t5404-tracking-branches.sh
index 20718d4..a6f60ac 100755
--- a/t/t5404-tracking-branches.sh
+++ b/t/t5404-tracking-branches.sh
@@ -10,6 +10,7 @@ test_expect_success 'setup' '
 	git commit -m 1 &&
 	git branch b1 &&
 	git branch b2 &&
+	git branch b3 &&
 	git clone . aa &&
 	git checkout b1 &&
 	echo b1 >>file &&
@@ -19,10 +20,13 @@ test_expect_success 'setup' '
 	git commit -a -m b2
 '
 
+start_dir="$(pwd)"
+
 test_expect_success 'check tracking branches updated correctly after push' '
 	cd aa &&
 	b1=$(git rev-parse origin/b1) &&
 	b2=$(git rev-parse origin/b2) &&
+	b3=$(git rev-parse origin/b3) &&
 	git checkout -b b1 origin/b1 &&
 	echo aa-b1 >>file &&
 	git commit -a -m aa-b1 &&
@@ -32,9 +36,27 @@ test_expect_success 'check tracking branches updated correctly after push' '
 	git checkout master &&
 	echo aa-master >>file &&
 	git commit -a -m aa-master &&
-	git push &&
-	test "$(git rev-parse origin/b1)" = "$b1" &&
-	test "$(git rev-parse origin/b2)" = "$b2"
+	{
+		git push
+		test "$(git rev-parse origin/b1)" = "$b1" &&
+		test "$(git rev-parse origin/b2)" = "$b2" &&
+		test "$(git rev-parse origin/b3)" = "$b3" &&
+		test "$(git rev-parse origin/master)" = \
+		"$(git rev-parse master)"
+	}
+'
+
+test_expect_success 'delete remote branch' '
+	git push origin :refs/heads/b3
+	{
+		git rev-parse --verify origin/b3
+		test $? != 0
+        } &&
+	cd "$start_dir" &&
+	{
+		git rev-parse refs/heads/b3
+		test $? != 0
+        }
 '
 
 test_done
-- 
1.5.3.5.692.ge1737
Previous: Jeff KingNext: Junio C Hamano
Message 9 of 22 in “Add a test checking if send-pack updated local tracking branches correctly”
  1. Add a test checking if send-pack updated local tracking branches correctlyAlex Riesen, Nov 12, 2007
  2. Update the tracking references only if they were succesfully updated on remoteAlex Riesen, Nov 12, 2007
  3. Jeff KingNov 13, 2007
  4. Alex RiesenNov 13, 2007
  5. Add a test for deleting remote branchesAlex Riesen, Nov 13, 2007
  6. Improved and extended t5404Alex Riesen, Nov 13, 2007
  7. Jeff KingNov 13, 2007
  8. Jeff KingNov 15, 2007
  9. Add test that checks diverse aspects of updating remote and tracking branchesAlex Riesen, Nov 15, 2007
  10. Junio C HamanoNov 14, 2007
  11. Alex RiesenNov 14, 2007
  12. Junio C HamanoNov 14, 2007
  13. Johannes SchindelinNov 14, 2007
  14. Alex RiesenNov 14, 2007
  15. Alex RiesenNov 14, 2007
  16. Johannes SchindelinNov 14, 2007
  17. Jeff KingNov 15, 2007
  18. Jeff KingNov 15, 2007
  19. Junio C HamanoNov 15, 2007
  20. Junio C HamanoNov 14, 2007
  21. Add test that checks diverse aspects of updating remote and tracking branchesAlex Riesen, Nov 14, 2007
  22. Junio C HamanoNov 14, 2007

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.