git-bisect is part of the git CM software. It is used to find which change broke something.
Questions tagged [git-bisect]
101 questions
6
votes
2 answers
How can I find out what commit(s) git bisect would try next?
In some cases during a git bisect session, testing a particular commit takes quite long (for instance, because I have to build a full release package and deploy it on a particularly strange machine). In fact, testing a build takes so long that I'd…
Frerich Raabe
- 90,689
- 19
- 115
- 207
6
votes
1 answer
What is the best way to do bisecting with subversion?
I tend to use the bisect command in git extensively. Now I want to do the same in a subversion repository. What is the best way to bisect a subversion repository?
Converting the svn repository to git is not an option because it is a fairly large one…
Fabian Jakobs
- 28,815
- 8
- 42
- 39
6
votes
2 answers
find the first or last commit a patch applies to
Assuming a patch was created from a specific commit in the past, and no longer applies to HEAD.
How can I find either the first or better the last commit in the history of HEAD, where this patch applies with "git apply" ?
Maybe something with git…
donquixote
- 4,877
- 3
- 31
- 54
5
votes
2 answers
Keeping git bisect on the ancestry path
I have a repository with a complicated tree of branches and merges, and I want to use git bisect to find when a bug was introduced.
I have a good commit and bad commit to start the bisect, where the good commit is an ancestor of the bad one.
I'd…
yairchu
- 23,680
- 7
- 69
- 109
4
votes
1 answer
How can git bisect pick a commit that doesn't have the first good commit as an ancestor? (using --first-parent)
I have a repository that uses a "trunk" flow with feature branches merging in and creating merge commits, and am using bisect to try find when issues were introduced. The issue identification process involves a comparison to results from a…
Joel Gibson
- 293
- 2
- 8
4
votes
1 answer
Unbounded git bisect
Is it possible to use git bisect with one of the bounds unspecified. For example if I discover something broken on HEAD but I suspect it worked at some point in the past, is there a way to tell git "try one commit ago, if that doesn't work try two…
Timmmm
- 88,195
- 71
- 364
- 509
4
votes
1 answer
git bisect not responding to commands
I'm on a separate branch titled redesign-test-fixes and I run git bisect start. After that, I test my bug and run git bisect bad. Terminal prints no output. I then run git bisect good. Same thing, no output is printed on terminal. It's as if bisect…
thank_you
- 11,001
- 19
- 101
- 185
4
votes
2 answers
How does --no-ff merge break bisect and blame?
Understanding the Git Workflow article says,
So you add a new rule: “When you merge in your feature branch, use
–no-ff to force a new commit.” This gets the job done, and you move
on.
Then one day you discover a critical bug in production, and…
sherlock
- 2,397
- 3
- 27
- 44
4
votes
1 answer
Find most recent good commit to pass to git bisect
Suppose I suddenly see something is failing on my Git repo. But I know that it was working a few commits ago, I just don't remember which commit. Instead of trying to find a "good" commit to do a git bisect, I would like to ask Git (perhaps with a…
Xu Wang
- 10,199
- 6
- 44
- 78
4
votes
1 answer
Is it possible to use git-bisect to track down an issue that might be in one of two repositories?
I work on a project that (for reasons outside the scope of this question) is separated between two git repositories. It's a web project, and has a common library layer (stored in repository A) and a specific project layer (stored in repository…
Andrew Ferrier
- 16,664
- 13
- 47
- 76
3
votes
1 answer
How can I see git bisect status of commits in git log?
I'm doing a git bisect, and I've found a few good and bad commits so far, which I can confirm by running git bisect log.
However, if I run git log for my branch git log --graph --decorate=full origin/master..mybranch I can see it display that a…
Andrew Grimm
- 78,473
- 57
- 200
- 338
3
votes
2 answers
git bisect with list of *uninteresting* paths
You can pass a list of paths to git bisect so that only commits changing those files are tested:
You can further cut down the number of trials, if you know what part
of the tree is involved in the problem you are tracking down, by
specifying…
Cactus
- 27,075
- 9
- 69
- 149
3
votes
1 answer
What does the last line of git bisect output mean?
I just ran a Git bisect and got the following output:
547b115c69ab2ac7fde285c9b5653cbd8309a930 is the first bad commit
commit 547b115c69ab2ac7fde285c9b5653cbd8309a930
Author: Václav Slavík
Date: Sat Mar 14 13:35:32 2015…
Alex Henrie
- 744
- 1
- 6
- 17
3
votes
1 answer
git bisect in one command
I think git bisect requires too much typing.
To check the last N commits I have to do:
user@host> git bisect start HEAD HEAD~10
user@host> git bisect run py.test -k test_something
...
c8bed9b56861ea626833637e11a216555d7e7414 is the first bad…
guettli
- 25,042
- 81
- 346
- 663
2
votes
2 answers
Is it possible to give `git bisect` a set of invalid commits to always skip?
On long project, there can be a whole bunch of commits it's not worth trying during bisection e.g.
commits which are known to be broken
commits which are otherwise part of a PR not guaranteeing validity
The second one can mostly be handled by…
Masklinn
- 34,759
- 3
- 38
- 57