How Git Bisect Makes Debugging Easier смотреть онлайн

Text Source:

#EASIER #DEBUGGING #MAKES #BISECT #GIT #HOW

How Git Bisect Makes Debugging Easier

Git bisect is a fantastic tool that can help make debugging a breeze. But very few people use it actively.

Delta debugging is the process of completing many debugging steps and in each one your goal is to eliminate half the "problem". You can think of it as the binary search of debugging. Or as Andreas Zeller (who coined the term) said:

Delta Debugging automates the scientific method of debugging. The basic idea of the scientific method is to establish a hypothesis on why something does not work. You test this hypothesis, and you refine or reject it depending on the test outcome. When debugging, people are doing this all the time. Manually. Delta Debugging automates this process. Git bisect is how we apply delta debugging with Git.

Let's assume we have a bug and we try to find the root cause. In every step of our investigation for a solution, we eliminate half the solution space. Configuration, code, input...anything. Here's an example to make it clearer.

This is essentially all epochs from the time we started the script (plus 3 seconds) until five minutes later, with a 3 second step.

and mark one commit as bad (usually the last one) and one commit as good. This would be the second commit when we generated the input:

After that, git bisect will split the history between the good and the bad commit in two. You can see that by doing git bisect visualize to see the commits that are considered the culprits, and

By then, you may either fix the bug or contact whomever committed the bad code/input/configuration. Here is how to get the details:

In love with Python, but I admire all the stacks that offer solutions without testing my patience. Avid productivity-ist, great-food worshipper, always-smiling. New tech junkie.

Learn to code for free. freeCodeCamp's open source curriculum has helped more than 40,000 people get jobs as