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

[PATCH] Bisect: add a "bisect replay" test case.

From
Christian Couder <chriscool@tuxfamily.org>
Date
Oct 16, 2007, 04:33 UTC
Message-ID
<20071016063313.17a6e7c1.chriscool@tuxfamily.org>
Signed-off-by: Christian Couder <chriscool@tuxfamily.org>
---
 t/t6030-bisect-porcelain.sh |    7 +++++++
 1 files changed, 7 insertions(+), 0 deletions(-)
	There is no bisect log/replay test case right now.
	Let's add one.
diff --git a/t/t6030-bisect-porcelain.sh b/t/t6030-bisect-porcelain.sh
index 7f41a46..49f3601 100755
--- a/t/t6030-bisect-porcelain.sh
+++ b/t/t6030-bisect-porcelain.sh
@@ -167,6 +167,13 @@ test_expect_success 'bisect dunno: add line and then a new test' '
 	git bisect dunno &&
 	git bisect good > my_bisect_log.txt &&
 	grep "$HASH5 is first bad commit" my_bisect_log.txt &&
+	git bisect log > log_to_replay.txt
+	git bisect reset
+'
+
+test_expect_success 'bisect dunno and bisect replay' '
+	git bisect replay log_to_replay.txt > my_bisect_log.txt &&
+	grep "$HASH5 is first bad commit" my_bisect_log.txt &&
 	git bisect reset
 '
 
-- 
1.5.3.3.136.g591d1-dirty
Message 1 of 1 in “Bisect: add a "bisect replay" test case.”
  1. Bisect: add a "bisect replay" test case.Christian Couder, Oct 16, 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.