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

[PATCH v3 1/2] Add a test to check that git ls-tree sets non-zero exit code on error.

From
Jon Seymour <jon.seymour@gmail.com>
Date
Jul 24, 2011, 14:59 UTC
Message-ID
<1311519554-16587-2-git-send-email-jon.seymour@gmail.com>
In-Reply-To
<1311519554-16587-1-git-send-email-jon.seymour@gmail.com>
Expected to fail at this commit, fixed by subsequent commit.

Additional tests of adhoc or uncategorised nature should be added to this file.

Improved-by: Jens Lehmann <Jens.Lehmann@web.de>
Improved-by: Junio C Hamano <gitster@pobox.com>
Signed-off-by: Jon Seymour <jon.seymour@gmail.com>
---
 t/t3103-ls-tree-misc.sh |   24 ++++++++++++++++++++++++
 1 files changed, 24 insertions(+), 0 deletions(-)
 create mode 100755 t/t3103-ls-tree-misc.sh
diff --git a/t/t3103-ls-tree-misc.sh b/t/t3103-ls-tree-misc.sh
new file mode 100755
index 0000000..c9c20f9
--- /dev/null
+++ b/t/t3103-ls-tree-misc.sh
@@ -0,0 +1,24 @@
+#!/bin/sh
+
+test_description='
+Miscellaneous tests for git ls-tree.
+
+	      1. git ls-tree fails in presence of tree damage.
+
+'
+
+. ./test-lib.sh
+
+test_expect_success 'setup' '
+	mkdir a &&
+	touch a/one &&
+	git add a/one &&
+	git commit -m test
+'
+
+test_expect_failure 'ls-tree fails with non-zero exit code on broken tree' '
+	rm -f .git/objects/5f/cffbd6e4c5c5b8d81f5e9314b20e338e3ffff5 &&
+	test_must_fail git ls-tree -r HEAD
+'
+
+test_done
-- 
1.7.6.347.gf855
Previous: Jon SeymourNext: Jon Seymour
Message 2 of 9 in “ls-tree: exit with non-zero status on error”
  1. 0/2 ls-tree: exit with non-zero status on errorJon Seymour, Jul 24, 2011
  2. 1/2 Add a test to check that git ls-tree sets non-zero exit code on error.Jon Seymour, Jul 24, 2011
  3. 2/2 Ensure git ls-tree exits with a non-zero exit code if read_tree_recursive fails.Jon Seymour, Jul 24, 2011
  4. Nguyen Thai Ngoc DuyJul 25, 2011
  5. Jon SeymourJul 25, 2011
  6. Nguyen Thai Ngoc DuyJul 25, 2011
  7. Andreas SchwabJul 25, 2011
  8. Jens LehmannJul 25, 2011
  9. Junio C HamanoJul 25, 2011

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.