Re: Git bisect does not find commit introducing the bug

From: Johannes Sixt <j6t@kdbg.org>
Date: Feb 19, 2017, 14:13 UTC
Message-ID: <d7bb866d-4a50-f75e-ff4c-bcdd54f75459@kdbg.org>
In-Reply-To: <CAMX8fZVeAEJ5tfCO_4Pebnq=rysaJ2xDMjH-9pjmPeF4FziLFw@mail.gmail.com>

Am 19.02.2017 um 12:32 schrieb Alex Hoffman:

> The assumption that there is no transition from bad to good in the
> graph did not hold in my example and it does not hold when a feature
> was recently introduced and gets broken relative shortly afterwards.

Then you must adjust your definition of "good": All commits that do not have the feature, yet, are "good": since they do not have the feature in the first place, they cannot have the breakage that you found in the feature.

That is exactly the situation in your original example! But you constructed the condition of goodness in such a simplistic way (depending on the presence of a string), that it was impossible to distinguish between "does not have the feature at all" and "has the feature, but it is broken".

-- Hannes