this post was submitted on 25 Jun 2023
26 points (100.0% liked)

Programming

13386 readers
141 users here now

All things programming and coding related. Subcommunity of Technology.

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago
MODERATORS
alyaza@beehaw.org
Hexorg@beehaw.org
remington@beehaw.org
26
Have you ever used git bisect? (programming.dev)
submitted 1 year ago by canpolat@programming.dev to c/programming@beehaw.org
20 comments fedilink hide all child comments
 

cross-posted from: https://programming.dev/post/214031

Have you ever used git bisect? If so, how did you use it? Did it help you find a problem which would otherwise be difficult to find? Story time, I guess?

you are viewing a single comment's thread
view the rest of the comments
[–] Nicktar@beehaw.org 4 points 1 year ago

Several times, sometimes to find out when an incompatibility was introduced in an upstream dependency to find the maximum compatible version, but usually to find the commit that introduced a strange bug.

The process is always the same... Write a unit test, start bisect, check test select next bisect step, repeat. If your last-known-good and first-known-bad are correct, it always worked for me.