3 ms·
A more generic term is "delta debugging", which has been around for a while. git bisect is one example of a tool which does it, another is Zeller's DD tool htt
by ajb 3y ago
A more generic term is "delta debugging", which has been around for a while. git bisect is one example of a tool which does it, another is Zeller's DD tool
https://www.st.cs.uni-saarland.de/dd/ https://www.st.cs.uni-saarland.de/dd/
It's also possible to do this is a Bayesian fashion.
- nerdponx 3y agoI'm very curious in the Bayesian approach to bisect debugging. Got a reference?
- ajb 3y agoFor git bisect, there is this: https://github.com/ealdwulf/bbchop https://github.com/ealdwulf/bbchop But it seems likely that heuristically picking a multiple of times to run the test produces similar results
- The_Colonel 3y agoMy guess would be that you don't always use the middle of the interval, but choose knowledge of the history to guide your choice of the tested revisions. e. g. recently I was debugging a problem, after two halvings, I saw there's a big refactoring in the remaining interval, so I picked the revision before/after.
- GuB-42 3y agodd? Isn't that a problem on UNIX systems where "dd" (the disk destroyer) is a standard command.
- ajb 3y agoNot really, it is shipped as DD.py