Post Syndicated from original https://lwn.net/Articles/877964/rss

Regressions are no fun; among other things, finding the source of a
regression among thousands of changes can be a needle-in-the-haystack sort
of problem. The git
bisect
command can help; it is a (relatively) easy way to sift through
large numbers of commits to find the one that introduces a regression. When it
works well, it can quickly point out the change that causes a specific
problem. Bisection is not a perfect tool, though; it can go badly wrong in
situations where a bug cannot be reliably reproduced. In an attempt to
make bisection more useful in such cases, Jan Kara is proposing to add “stochastic
bisection” support to Git.