[PATCH] Making it easier to find which change introduced a bug
This adds a new "git bisect" command.
- "git bisect start"
start bisection search.
- "git bisect bad <rev>"
mark some version known-bad (if no arguments, then current HEAD)
- "git bisect good <revs>..."
mark some versions known-good (if no arguments, then current HEAD)
- "git bisect reset <branch>"
done with bisection search and go back to your work (if
no arguments, then "master").
The way you use it is:
git bisect start
git bisect bad # Current version is bad
git bisect good v2.6.13-rc2 # v2.6.13-rc2 was the last version
# tested that was good
When you give at least one bad and one good versions, it will
bisect the revision tree and say something like:
Bisecting: 675 revisions left to test after this
and check out the state in the middle. Now, compile that kernel, and boot
it. Now, let's say that this booted kernel works fine, then just do
git bisect good # this one is good
which will now say
Bisecting: 337 revisions left to test after this
and you continue along, compiling that one, testing it, and depending on
whether it is good or bad, you say "git bisect good" or "git bisect bad",
and ask for the next bisection.
Until you have no more left, and you'll have been left with the first bad
kernel rev in "refs/bisect/bad".
Oh, and then after you want to reset to the original head, do a
git bisect reset
to get back to the master branch, instead of being in one of the bisection
branches ("git bisect start" will do that for you too, actually: it will
reset the bisection state, and before it does that it checks that you're
not using some old bisection branch).
Not really any harder than doing series of "quilt push" and "quilt pop",
now is it?
[jc: This patch is a rework based on what Linus posted to the
list. The changes are:
- The original introduced four separate commands, which was
three too many, so I merged them into one with subcommands.
- Since the next thing you would want to do after telling it
"bad" and "good" is always to bisect, this version does it
automatically for you.
- I think the termination condition was wrong. The original
version checked if the set of revisions reachable from next
bisection but not rechable from any of the known good ones
is empty, but if the current bisection was a bad one, this
would not terminate, so I changed it to terminate it when
the set becomes a singleton or empty.
- Removed the use of shell array variable.
]
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Signed-off-by: Junio C Hamano <junkio@cox.net>
2005-07-30 21:08:20 +04:00
|
|
|
#!/bin/sh
|
2005-12-11 12:55:49 +03:00
|
|
|
|
2017-11-12 12:30:38 +03:00
|
|
|
USAGE='[help|start|bad|good|new|old|terms|skip|next|reset|visualize|view|replay|log|run]'
|
2008-04-11 07:55:21 +04:00
|
|
|
LONG_USAGE='git bisect help
|
2011-08-05 15:31:30 +04:00
|
|
|
print this long help message.
|
2020-08-28 18:31:19 +03:00
|
|
|
git bisect start [--term-{new,bad}=<term> --term-{old,good}=<term>]
|
2020-08-22 23:32:03 +03:00
|
|
|
[--no-checkout] [--first-parent] [<bad> [<good>...]] [--] [<pathspec>...]
|
2011-08-05 15:31:30 +04:00
|
|
|
reset bisect state and start bisection.
|
2015-06-29 18:40:33 +03:00
|
|
|
git bisect (bad|new) [<rev>]
|
|
|
|
mark <rev> a known-bad revision/
|
|
|
|
a revision after change in a given property.
|
|
|
|
git bisect (good|old) [<rev>...]
|
|
|
|
mark <rev>... known-good revisions/
|
|
|
|
revisions before change in a given property.
|
2015-06-29 18:40:34 +03:00
|
|
|
git bisect terms [--term-good | --term-bad]
|
|
|
|
show the terms used for old and new commits (default: bad, good)
|
2008-12-02 16:53:51 +03:00
|
|
|
git bisect skip [(<rev>|<range>)...]
|
2011-08-05 15:31:30 +04:00
|
|
|
mark <rev>... untestable revisions.
|
2007-04-04 09:12:02 +04:00
|
|
|
git bisect next
|
2011-08-05 15:31:30 +04:00
|
|
|
find next bisection to test and check it out.
|
2009-10-14 01:02:24 +04:00
|
|
|
git bisect reset [<commit>]
|
2011-08-05 15:31:30 +04:00
|
|
|
finish bisection search and go back to commit.
|
2017-11-12 12:30:38 +03:00
|
|
|
git bisect (visualize|view)
|
2011-08-05 15:31:30 +04:00
|
|
|
show bisect status in gitk.
|
2007-04-04 09:12:02 +04:00
|
|
|
git bisect replay <logfile>
|
2011-08-05 15:31:30 +04:00
|
|
|
replay bisection log.
|
2007-04-04 09:12:02 +04:00
|
|
|
git bisect log
|
2011-08-05 15:31:30 +04:00
|
|
|
show bisect log.
|
2007-04-04 09:12:02 +04:00
|
|
|
git bisect run <cmd>...
|
2011-08-05 15:31:30 +04:00
|
|
|
use <cmd>... to automatically bisect.
|
2008-04-11 07:55:21 +04:00
|
|
|
|
|
|
|
Please use "git help bisect" to get the full man page.'
|
2005-12-11 12:55:49 +03:00
|
|
|
|
2007-11-06 12:50:02 +03:00
|
|
|
OPTIONS_SPEC=
|
2005-11-24 11:12:11 +03:00
|
|
|
. git-sh-setup
|
[PATCH] Making it easier to find which change introduced a bug
This adds a new "git bisect" command.
- "git bisect start"
start bisection search.
- "git bisect bad <rev>"
mark some version known-bad (if no arguments, then current HEAD)
- "git bisect good <revs>..."
mark some versions known-good (if no arguments, then current HEAD)
- "git bisect reset <branch>"
done with bisection search and go back to your work (if
no arguments, then "master").
The way you use it is:
git bisect start
git bisect bad # Current version is bad
git bisect good v2.6.13-rc2 # v2.6.13-rc2 was the last version
# tested that was good
When you give at least one bad and one good versions, it will
bisect the revision tree and say something like:
Bisecting: 675 revisions left to test after this
and check out the state in the middle. Now, compile that kernel, and boot
it. Now, let's say that this booted kernel works fine, then just do
git bisect good # this one is good
which will now say
Bisecting: 337 revisions left to test after this
and you continue along, compiling that one, testing it, and depending on
whether it is good or bad, you say "git bisect good" or "git bisect bad",
and ask for the next bisection.
Until you have no more left, and you'll have been left with the first bad
kernel rev in "refs/bisect/bad".
Oh, and then after you want to reset to the original head, do a
git bisect reset
to get back to the master branch, instead of being in one of the bisection
branches ("git bisect start" will do that for you too, actually: it will
reset the bisection state, and before it does that it checks that you're
not using some old bisection branch).
Not really any harder than doing series of "quilt push" and "quilt pop",
now is it?
[jc: This patch is a rework based on what Linus posted to the
list. The changes are:
- The original introduced four separate commands, which was
three too many, so I merged them into one with subcommands.
- Since the next thing you would want to do after telling it
"bad" and "good" is always to bisect, this version does it
automatically for you.
- I think the termination condition was wrong. The original
version checked if the set of revisions reachable from next
bisection but not rechable from any of the known good ones
is empty, but if the current bisection was a bad one, this
would not terminate, so I changed it to terminate it when
the set becomes a singleton or empty.
- Removed the use of shell array variable.
]
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Signed-off-by: Junio C Hamano <junkio@cox.net>
2005-07-30 21:08:20 +04:00
|
|
|
|
2015-06-29 18:40:29 +03:00
|
|
|
TERM_BAD=bad
|
|
|
|
TERM_GOOD=good
|
2008-02-10 16:59:50 +03:00
|
|
|
|
2015-06-29 18:40:30 +03:00
|
|
|
get_terms () {
|
|
|
|
if test -s "$GIT_DIR/BISECT_TERMS"
|
|
|
|
then
|
|
|
|
{
|
|
|
|
read TERM_BAD
|
|
|
|
read TERM_GOOD
|
|
|
|
} <"$GIT_DIR/BISECT_TERMS"
|
|
|
|
fi
|
|
|
|
}
|
|
|
|
|
[PATCH] Making it easier to find which change introduced a bug
This adds a new "git bisect" command.
- "git bisect start"
start bisection search.
- "git bisect bad <rev>"
mark some version known-bad (if no arguments, then current HEAD)
- "git bisect good <revs>..."
mark some versions known-good (if no arguments, then current HEAD)
- "git bisect reset <branch>"
done with bisection search and go back to your work (if
no arguments, then "master").
The way you use it is:
git bisect start
git bisect bad # Current version is bad
git bisect good v2.6.13-rc2 # v2.6.13-rc2 was the last version
# tested that was good
When you give at least one bad and one good versions, it will
bisect the revision tree and say something like:
Bisecting: 675 revisions left to test after this
and check out the state in the middle. Now, compile that kernel, and boot
it. Now, let's say that this booted kernel works fine, then just do
git bisect good # this one is good
which will now say
Bisecting: 337 revisions left to test after this
and you continue along, compiling that one, testing it, and depending on
whether it is good or bad, you say "git bisect good" or "git bisect bad",
and ask for the next bisection.
Until you have no more left, and you'll have been left with the first bad
kernel rev in "refs/bisect/bad".
Oh, and then after you want to reset to the original head, do a
git bisect reset
to get back to the master branch, instead of being in one of the bisection
branches ("git bisect start" will do that for you too, actually: it will
reset the bisection state, and before it does that it checks that you're
not using some old bisection branch).
Not really any harder than doing series of "quilt push" and "quilt pop",
now is it?
[jc: This patch is a rework based on what Linus posted to the
list. The changes are:
- The original introduced four separate commands, which was
three too many, so I merged them into one with subcommands.
- Since the next thing you would want to do after telling it
"bad" and "good" is always to bisect, this version does it
automatically for you.
- I think the termination condition was wrong. The original
version checked if the set of revisions reachable from next
bisection but not rechable from any of the known good ones
is empty, but if the current bisection was a bad one, this
would not terminate, so I changed it to terminate it when
the set becomes a singleton or empty.
- Removed the use of shell array variable.
]
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Signed-off-by: Junio C Hamano <junkio@cox.net>
2005-07-30 21:08:20 +04:00
|
|
|
case "$#" in
|
|
|
|
0)
|
2011-08-05 15:31:30 +04:00
|
|
|
usage ;;
|
[PATCH] Making it easier to find which change introduced a bug
This adds a new "git bisect" command.
- "git bisect start"
start bisection search.
- "git bisect bad <rev>"
mark some version known-bad (if no arguments, then current HEAD)
- "git bisect good <revs>..."
mark some versions known-good (if no arguments, then current HEAD)
- "git bisect reset <branch>"
done with bisection search and go back to your work (if
no arguments, then "master").
The way you use it is:
git bisect start
git bisect bad # Current version is bad
git bisect good v2.6.13-rc2 # v2.6.13-rc2 was the last version
# tested that was good
When you give at least one bad and one good versions, it will
bisect the revision tree and say something like:
Bisecting: 675 revisions left to test after this
and check out the state in the middle. Now, compile that kernel, and boot
it. Now, let's say that this booted kernel works fine, then just do
git bisect good # this one is good
which will now say
Bisecting: 337 revisions left to test after this
and you continue along, compiling that one, testing it, and depending on
whether it is good or bad, you say "git bisect good" or "git bisect bad",
and ask for the next bisection.
Until you have no more left, and you'll have been left with the first bad
kernel rev in "refs/bisect/bad".
Oh, and then after you want to reset to the original head, do a
git bisect reset
to get back to the master branch, instead of being in one of the bisection
branches ("git bisect start" will do that for you too, actually: it will
reset the bisection state, and before it does that it checks that you're
not using some old bisection branch).
Not really any harder than doing series of "quilt push" and "quilt pop",
now is it?
[jc: This patch is a rework based on what Linus posted to the
list. The changes are:
- The original introduced four separate commands, which was
three too many, so I merged them into one with subcommands.
- Since the next thing you would want to do after telling it
"bad" and "good" is always to bisect, this version does it
automatically for you.
- I think the termination condition was wrong. The original
version checked if the set of revisions reachable from next
bisection but not rechable from any of the known good ones
is empty, but if the current bisection was a bad one, this
would not terminate, so I changed it to terminate it when
the set becomes a singleton or empty.
- Removed the use of shell array variable.
]
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Signed-off-by: Junio C Hamano <junkio@cox.net>
2005-07-30 21:08:20 +04:00
|
|
|
*)
|
2011-08-05 15:31:30 +04:00
|
|
|
cmd="$1"
|
2015-06-29 18:40:30 +03:00
|
|
|
get_terms
|
2011-08-05 15:31:30 +04:00
|
|
|
shift
|
|
|
|
case "$cmd" in
|
|
|
|
help)
|
|
|
|
git bisect -h ;;
|
|
|
|
start)
|
2020-10-15 16:38:32 +03:00
|
|
|
git bisect--helper --bisect-start "$@" ;;
|
2015-06-29 18:40:33 +03:00
|
|
|
bad|good|new|old|"$TERM_BAD"|"$TERM_GOOD")
|
2020-10-15 16:38:35 +03:00
|
|
|
git bisect--helper --bisect-state "$cmd" "$@" ;;
|
2011-08-05 15:31:30 +04:00
|
|
|
skip)
|
2021-02-04 00:54:37 +03:00
|
|
|
git bisect--helper --bisect-skip "$@" || exit;;
|
2011-08-05 15:31:30 +04:00
|
|
|
next)
|
|
|
|
# Not sure we want "next" at the UI level anymore.
|
2020-09-24 15:33:40 +03:00
|
|
|
git bisect--helper --bisect-next "$@" || exit ;;
|
2011-08-05 15:31:30 +04:00
|
|
|
visualize|view)
|
2021-09-13 20:39:02 +03:00
|
|
|
git bisect--helper --bisect-visualize "$@" || exit;;
|
2011-08-05 15:31:30 +04:00
|
|
|
reset)
|
2019-01-02 18:38:31 +03:00
|
|
|
git bisect--helper --bisect-reset "$@" ;;
|
2011-08-05 15:31:30 +04:00
|
|
|
replay)
|
2021-02-04 00:54:33 +03:00
|
|
|
git bisect--helper --bisect-replay "$@" || exit;;
|
2011-08-05 15:31:30 +04:00
|
|
|
log)
|
2021-02-04 00:54:32 +03:00
|
|
|
git bisect--helper --bisect-log || exit ;;
|
2011-08-05 15:31:30 +04:00
|
|
|
run)
|
2021-09-13 20:39:03 +03:00
|
|
|
git bisect--helper --bisect-run "$@" || exit;;
|
2015-06-29 18:40:34 +03:00
|
|
|
terms)
|
2019-01-02 18:38:35 +03:00
|
|
|
git bisect--helper --bisect-terms "$@" || exit;;
|
2011-08-05 15:31:30 +04:00
|
|
|
*)
|
|
|
|
usage ;;
|
|
|
|
esac
|
[PATCH] Making it easier to find which change introduced a bug
This adds a new "git bisect" command.
- "git bisect start"
start bisection search.
- "git bisect bad <rev>"
mark some version known-bad (if no arguments, then current HEAD)
- "git bisect good <revs>..."
mark some versions known-good (if no arguments, then current HEAD)
- "git bisect reset <branch>"
done with bisection search and go back to your work (if
no arguments, then "master").
The way you use it is:
git bisect start
git bisect bad # Current version is bad
git bisect good v2.6.13-rc2 # v2.6.13-rc2 was the last version
# tested that was good
When you give at least one bad and one good versions, it will
bisect the revision tree and say something like:
Bisecting: 675 revisions left to test after this
and check out the state in the middle. Now, compile that kernel, and boot
it. Now, let's say that this booted kernel works fine, then just do
git bisect good # this one is good
which will now say
Bisecting: 337 revisions left to test after this
and you continue along, compiling that one, testing it, and depending on
whether it is good or bad, you say "git bisect good" or "git bisect bad",
and ask for the next bisection.
Until you have no more left, and you'll have been left with the first bad
kernel rev in "refs/bisect/bad".
Oh, and then after you want to reset to the original head, do a
git bisect reset
to get back to the master branch, instead of being in one of the bisection
branches ("git bisect start" will do that for you too, actually: it will
reset the bisection state, and before it does that it checks that you're
not using some old bisection branch).
Not really any harder than doing series of "quilt push" and "quilt pop",
now is it?
[jc: This patch is a rework based on what Linus posted to the
list. The changes are:
- The original introduced four separate commands, which was
three too many, so I merged them into one with subcommands.
- Since the next thing you would want to do after telling it
"bad" and "good" is always to bisect, this version does it
automatically for you.
- I think the termination condition was wrong. The original
version checked if the set of revisions reachable from next
bisection but not rechable from any of the known good ones
is empty, but if the current bisection was a bad one, this
would not terminate, so I changed it to terminate it when
the set becomes a singleton or empty.
- Removed the use of shell array variable.
]
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Signed-off-by: Junio C Hamano <junkio@cox.net>
2005-07-30 21:08:20 +04:00
|
|
|
esac
|