It won't, in such cases.
But you can also git reset --hard another_commit_id (while doing git
bisect) if it fixes this problem (e.g. some next commit).
And you can skip uninteresting parts of the tree when starting git
bisect (though if the cause is in skipped parts, the results will be