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

Re: 'git bisect run' not fully automatic when a merge base must be tested

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 24, 2024, 21:42 UTC
Message-ID
<xmqq34sfqpcf.fsf@gitster.g>
In-Reply-To
<CAP8UFD2dNix6OMzCR5Ao8YLD-OVbcOfZOP90G7-QRx=OtRAoYw@mail.gmail.com>
Christian Couder <christian.couder@gmail.com> writes:
> I think the merge bases should only be checked at the beginning of a
> bisection. So it is strange that it happened so late after it was
> started.

Using cherry-pick to alter the shape of the history being bisected may confuse the algorithm to find the next step to test. But if it is not "confused" but "due to dynamic expansion of the search space, we ended up in a forked history that requires a merge-base test" that is a legitimate condition, then I tend to agree with Philippe that it should be automatically tested during "bisect run".

Previous: Christian Couder
Message 3 of 3 in “'git bisect run' not fully automatic when a merge base must be tested”
  1. Philippe BlainMar 24, 2024
  2. Christian CouderMar 24, 2024
  3. Junio C HamanoMar 24, 2024

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.