3 ms·
The main impediments against git bisect aren't commits that don't build; git bisect has a working solution for that. The main impediments are external dependen
by kazinator 4y ago
The main impediments against git bisect aren't commits that don't build; git bisect has a working solution for that.
The main impediments are external dependencies: the things contributing to the behavior change you're looking for which are not in the git repo you are bisecting:
- components from other git repos it depends on which were changing in parallel at around the time the problem showed up
- platform/toolchain and other dependencies; maybe the problem showed up because of a compiler upgrade.
Plus other things:
- difficult reproducibility of the issue being tested.
- multiple unrelated problems masquerading under the manifestation that you're actually testing for.
Regarding buildable commits; if you want a buildable commit to stay buildable, it has to reference the exact toolchain that was used, which has to be available. A commit that built with GCC 4 may not build with your GCC 12 today.
I've done bisects going back 10, 12 years.