Skip to main content
You use bisect to find the commit that introduced a bug. It checks out the middle commit between one that has the bug and an older one that does not, then repeats on the half you mark. The search follows each commit’s previous commit, so it stays on one line of history. If the bug came in through a merge, the result is that merge. Check out the other branch and run bisect there to continue.
Start a search, mark the current commit as bad, and name an older commit that does not have the bug:
Test the files, then mark what you found:
dv bisect run runs a command at each step.
  • Exit code 0 means the bug is not in this commit.
  • Exit code 125 skips a commit you cannot test.
  • Exit codes 1 to 127 mean the bug is in this commit.
  • Exit code 128 or higher stops the search.
The command runs in the workspace root. DV_BISECT_COMMIT is the commit under test. Put -- before arguments that start with a dash. Files the command creates are discarded before the next checkout.
Uncommitted changes are refused before the first test, so a local edit cannot hide the commit under test. dv bisect reset stops the search and checks out the branch or commit you were on when it started.