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

Re: FYI, git output messages are being used by other tooling

From
Steven Rostedt <rostedt@goodmis.org>
Date
Oct 20, 2026, 19:23 UTC
Message-ID
<20261020152354.165ad128@gandalf.local.home>
In-Reply-To
<xmqq8q3sw75e.fsf@gitster.g>

On Tue, 20 Oct 2026 11:37:01 -0700 Junio C Hamano <gitster@pobox.com> wrote:

Show 18 quoted lines
> Steven Rostedt <rostedt@goodmis.org> writes:
> 
> > Hi,
> >
> > I just want to let you folks know that ktest.pl (tools/testing/ktest/ in
> > the Linux kernel repository) parses the output of git to display the first
> > bad commit found in an automated git bisect.
> >
> > The output was recently updated via: 0c0f93e7fa64 ("bisect: print bisect
> > terms in single quotes") which made ktest.pl fail to find the bad commit.
> >
> > The change is being addressed:
> >
> >   https://lore.kernel.org/all/20261009-ktest-git-bisect-v1-1-1d1428f6cbf4@marliere.net/
> >
> > But I figured it would be good for you to know about this dependency.  
> 
> Shouldn't the script instead seeing "git show bisect/bad" instead?

Hmm, it also is used to see if the bisect finished or not. It looks at the output of the last git bisect action and has:

    if ($output =~ m/^(Bisecting: .*\(roughly \d+ steps?\))\s+\[([[:xdigit:]]+)\]/) {
	doprint "$1 [$2]\n";
    } elsif ($output =~ m/^([[:xdigit:]]+) is the first bad commit/) {
	$bisect_bad_commit = $1;
	doprint "Found bad commit... $1\n";
	return 0;
    } else {
	# we already logged it, just print it now.
	print $output;
    }
    return 1;

Where returning 0 means the bad commit has been found. Otherwise it keeps looping.

Is there a git command to know if the bad bisect has been found or not?
-- Steve
Previous: Andreas SchwabNext: Kristoffer Haugsbakk
Message 7 of 12 in “FYI, git output messages are being used by other tooling”
  1. Steven RostedtOct 20, 2026
  2. Junio C HamanoOct 20, 2026
  3. Steven RostedtOct 20, 2026
  4. Theodore TsoOct 20, 2026
  5. Junio C HamanoOct 21, 2026
  6. Andreas SchwabOct 21, 2026
  7. Steven RostedtOct 20, 2026
  8. Kristoffer HaugsbakkOct 20, 2026
  9. Steven RostedtOct 20, 2026
  10. Theodore TsoOct 20, 2026
  11. Kristoffer HaugsbakkOct 21, 2026
  12. Kristoffer HaugsbakkOct 20, 2026

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.