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

[PATCH] t5701: do not get stuck in empty-push/

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Apr 27, 2009, 22:12 UTC
Message-ID
<3fb85879424c45d4112e08ae4d20d55fd5b58171.1240870321u.git.johannes.schindelin@gmx.de>
In-Reply-To
<cover.1240870321u.git.johannes.schindelin@gmx.de>

When keeping own tests in a private Git tree, it is nice to assume that the current working directory will not change just because another test was added in the upstream repository.

Fix a162e78 in that respect.
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
---
 t/t5701-clone-local.sh |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/t/t5701-clone-local.sh b/t/t5701-clone-local.sh
index f26b511..19b5c0d 100755
--- a/t/t5701-clone-local.sh
+++ b/t/t5701-clone-local.sh
@@ -138,8 +138,8 @@ test_expect_success 'clone empty repository, and then push should not segfault.'
 	mkdir empty &&
 	(cd empty && git init) &&
 	git clone empty empty-clone &&
-	cd empty-clone &&
-	test_must_fail git push
+	(cd empty-clone &&
+	test_must_fail git push)
 '
 
 test_done
-- 
1.6.3.rc3.326.g039c1
Message 1 of 1 in “t5701: do not get stuck in empty-push/”
  1. t5701: do not get stuck in empty-push/Johannes Schindelin, Apr 27, 2009

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.