Git bisect says Bisecting: a merge base needs to be checked

Question

I did bisect git and got the result

Bisecting: a merge base must be tested
[bbdaf1111eea5365c0c94d6045d6263aab718925] Fix display bug with main-stage

How can I continue?

Answer 1

This will happen if a given good and bad edition are not direct descendants of each other.

Let's assume that the repository looks like this (using sample names for commits):

* dffa2 good-commit
* b38f4 a2
* cc19f a1
| * d1f17 bad-commit
| * fbd1f b2
| * f66cc b1
|/
* 09f66 merge-base-commit

What does a merge base mean?

Since the term "merge base" is used in the message, it may be useful to understand this term in order to understand the message. The merge base of two or more commits is the last commit that is the parent of all these commits.

, , " " . , " ", , .

:

$ git bisect start
$ git bisect good good-commit
$ git bisect bad bad-commit
Bisecting: a merge base must be tested
[09f66] merge-base-commit

, , ( bad ), :

good-commit bad-commit

, merge-base-commit. , , good-commit bad-commit. good-commit a1, a2 good-commit , , , , :

$ git bisect bad
The merge base merge-base-commit is bad.
This means the bug has been fixed between 09f66 and [dffa2].

merge-base-commit bad-commit

, , b1, b2 bad-commit. bisect merge-base-commit bad-commit, , :

$ git bisect good
Bisecting: 0 revisions left to test after this (roughly 1 step)
[fbd1f] b2

Answer 2

git bisect, . "", , , /, .

git bisect good

git bisect bad

.

Answer 3

Let it start, it is normal if there are plums along the path that needs to be divided in half.