Re: [PATCH v7 04/10] t6099, t6600: add side-exhaustion regression tests
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Aug 6, 2026, 16:11 UTC
- Message-ID
- <xmqqa4qzmdp7.fsf@gitster.g>
- In-Reply-To
- <e8565ce0203e7f94f3f1ac193eb1fd703fe50463.1786013982.git.gitgitgadget@gmail.com>
"Kristofer Karlsson via GitGitGadget" <gitgitgadget@gmail.com> writes:
Show 19 quoted lines
> From: Kristofer Karlsson <krka@spotify.com> > > Add t6099 to test the case where multiple merge-base candidates exist > and one is an ancestor of another. This exercises the side-exhaustion > optimization in paint_down_to_common together with the > remove_redundant safety net in get_merge_bases_many_0. > > Add a mixed finite/INFINITY test to t6600 where one tip is outside > the commit-graph (INFINITY generation) and the other is inside. > This exercises the region transition: the walk starts in the > INFINITY region where side-exhaustion is disabled, then crosses > into the finite region where it can fire. > > Signed-off-by: Kristofer Karlsson <krka@spotify.com> > --- > t/meson.build | 1 + > t/t6099-merge-base-side-exhaustion.sh | 82 +++++++++++++++++++++++++++ > 2 files changed, 83 insertions(+) > create mode 100755 t/t6099-merge-base-side-exhaustion.sh
The log message and diffstat contradict each other. The addition to 't6600' happens a bit later at step 6/10, which presumably introduces this finite/infinite distinction, does it not?