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

[PATCH v4 08/12] bisect: libify `bisect_checkout`

From
Miriam Rubio <mirucam@gmail.com>
Date
Feb 17, 2020, 08:40 UTC
Message-ID
<20200217084039.78215-9-mirucam@gmail.com>
In-Reply-To
<20200217084039.78215-1-mirucam@gmail.com>
From: Pranit Bauva <pranit.bauva@gmail.com>

Since we want to get rid of git-bisect.sh, it would be necessary to convert those exit() calls to return statements so that errors can be reported.

Emulate try catch in C by converting `exit(<positive-value>)` to `return <negative-value>`. Follow POSIX conventions to return <negative-value> to indicate error.

Turn `exit()` to `return` calls in `bisect_checkout()`. Changes related to return values have no bad side effects on the code that calls `bisect_checkout()`.

Mentored-by: Christian Couder <chriscool@tuxfamily.org>
Mentored-by: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Signed-off-by: Pranit Bauva <pranit.bauva@gmail.com>
Signed-off-by: Tanushree Tumane <tanushreetumane@gmail.com>
Signed-off-by: Miriam Rubio <mirucam@gmail.com>
---
 bisect.c | 19 +++++++++++++++----
 1 file changed, 15 insertions(+), 4 deletions(-)
diff --git a/bisect.c b/bisect.c
index 85bda3500b..f6582ddfed 100644
--- a/bisect.c
+++ b/bisect.c
@@ -704,9 +704,10 @@ static int is_expected_rev(const struct object_id *oid)
 	return res;
 }
 
-static int bisect_checkout(const struct object_id *bisect_rev, int no_checkout)
+static enum bisect_error bisect_checkout(const struct object_id *bisect_rev, int no_checkout)
 {
 	char bisect_rev_hex[GIT_MAX_HEXSZ + 1];
+	enum bisect_error res = BISECT_OK;
 
 	memcpy(bisect_rev_hex, oid_to_hex(bisect_rev), the_hash_algo->hexsz + 1);
 	update_ref(NULL, "BISECT_EXPECTED_REV", bisect_rev, NULL, 0, UPDATE_REFS_DIE_ON_ERR);
@@ -716,14 +717,24 @@ static int bisect_checkout(const struct object_id *bisect_rev, int no_checkout)
 		update_ref(NULL, "BISECT_HEAD", bisect_rev, NULL, 0,
 			   UPDATE_REFS_DIE_ON_ERR);
 	} else {
-		int res;
 		res = run_command_v_opt(argv_checkout, RUN_GIT_CMD);
 		if (res)
-			exit(res);
+			/*
+			 * Errors in `run_command()` itself, signaled by res < 0,
+			 * and errors in the child process, signaled by res > 0
+			 * can both be treated as regular BISECT_FAILURE (-1).
+			 */
+			return -abs(res);
 	}
 
 	argv_show_branch[1] = bisect_rev_hex;
-	return run_command_v_opt(argv_show_branch, RUN_GIT_CMD);
+	res = run_command_v_opt(argv_show_branch, RUN_GIT_CMD);
+	/*
+	 * Errors in `run_command()` itself, signaled by res < 0,
+	 * and errors in the child process, signaled by res > 0
+	 * can both be treated as regular BISECT_FAILURE (-1).
+	 */
+	return -abs(res);
 }
 
 static struct commit *get_commit_reference(struct repository *r,
-- 
2.25.0
Previous: Miriam RubioNext: Miriam Rubio
Message 8 of 14 in “Finish converting git bisect to C part 1”
  1. Miriam RubioFeb 17, 2020
  2. 01/12 bisect--helper: convert `vocab_*` char pointers to char arraysMiriam Rubio, Feb 17, 2020
  3. 03/12 bisect: use the standard 'if (!var)' way to check for 0Miriam Rubio, Feb 17, 2020
  4. 02/12 bisect--helper: change `retval` to `res`Miriam Rubio, Feb 17, 2020
  5. 05/12 bisect: add enum to represent bisect returning codesMiriam Rubio, Feb 17, 2020
  6. 04/12 bisect--helper: introduce new `decide_next()` functionMiriam Rubio, Feb 17, 2020
  7. 06/12 bisect--helper: return error codes from `cmd_bisect__helper()`Miriam Rubio, Feb 17, 2020
  8. 08/12 bisect: libify `bisect_checkout`Miriam Rubio, Feb 17, 2020
  9. 07/12 bisect: libify `exit_if_skipped_commits` to `error_if_skipped*` and its dependentsMiriam Rubio, Feb 17, 2020
  10. 10/12 bisect: libify `check_good_are_ancestors_of_bad` and its dependentsMiriam Rubio, Feb 17, 2020
  11. 09/12 bisect: libify `check_merge_bases` and its dependentsMiriam Rubio, Feb 17, 2020
  12. 11/12 bisect: libify `handle_bad_merge_base` and its dependentsMiriam Rubio, Feb 17, 2020
  13. 12/12 bisect: libify `bisect_next_all`Miriam Rubio, Feb 17, 2020
  14. Junio C HamanoFeb 19, 2020

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.