2007-03-23 15:49:59 +08:00
|
|
|
#!/bin/sh
|
|
|
|
#
|
|
|
|
# Copyright (c) 2007 Christian Couder
|
|
|
|
#
|
2008-09-03 16:59:29 +08:00
|
|
|
test_description='Tests git bisect functionality'
|
2007-03-23 15:49:59 +08:00
|
|
|
|
2007-04-06 14:27:44 +08:00
|
|
|
exec </dev/null
|
|
|
|
|
2007-03-23 15:49:59 +08:00
|
|
|
. ./test-lib.sh
|
|
|
|
|
|
|
|
add_line_into_file()
|
|
|
|
{
|
|
|
|
_line=$1
|
|
|
|
_file=$2
|
|
|
|
|
|
|
|
if [ -f "$_file" ]; then
|
|
|
|
echo "$_line" >> $_file || return $?
|
|
|
|
MSG="Add <$_line> into <$_file>."
|
|
|
|
else
|
|
|
|
echo "$_line" > $_file || return $?
|
|
|
|
git add $_file || return $?
|
|
|
|
MSG="Create file <$_file> with <$_line> inside."
|
|
|
|
fi
|
|
|
|
|
2007-04-24 13:10:47 +08:00
|
|
|
test_tick
|
2008-09-03 16:59:29 +08:00
|
|
|
git commit --quiet -m "$MSG" $_file
|
2007-03-23 15:49:59 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
HASH1=
|
2007-04-24 13:10:47 +08:00
|
|
|
HASH2=
|
2007-03-23 15:49:59 +08:00
|
|
|
HASH3=
|
|
|
|
HASH4=
|
|
|
|
|
2007-04-24 13:10:47 +08:00
|
|
|
test_expect_success 'set up basic repo with 1 file (hello) and 4 commits' '
|
|
|
|
add_line_into_file "1: Hello World" hello &&
|
|
|
|
HASH1=$(git rev-parse --verify HEAD) &&
|
2007-03-23 15:49:59 +08:00
|
|
|
add_line_into_file "2: A new day for git" hello &&
|
2007-04-24 13:10:47 +08:00
|
|
|
HASH2=$(git rev-parse --verify HEAD) &&
|
2007-03-23 15:49:59 +08:00
|
|
|
add_line_into_file "3: Another new day for git" hello &&
|
2007-04-24 13:10:47 +08:00
|
|
|
HASH3=$(git rev-parse --verify HEAD) &&
|
2007-03-23 15:49:59 +08:00
|
|
|
add_line_into_file "4: Ciao for now" hello &&
|
2007-04-24 13:10:47 +08:00
|
|
|
HASH4=$(git rev-parse --verify HEAD)
|
|
|
|
'
|
2007-03-23 15:49:59 +08:00
|
|
|
|
2007-04-06 14:27:44 +08:00
|
|
|
test_expect_success 'bisect starts with only one bad' '
|
2007-04-06 13:52:37 +08:00
|
|
|
git bisect reset &&
|
|
|
|
git bisect start &&
|
2007-04-06 14:27:44 +08:00
|
|
|
git bisect bad $HASH4 &&
|
|
|
|
git bisect next
|
2007-04-06 13:52:37 +08:00
|
|
|
'
|
|
|
|
|
2007-04-17 12:51:48 +08:00
|
|
|
test_expect_success 'bisect does not start with only one good' '
|
2007-04-06 13:52:37 +08:00
|
|
|
git bisect reset &&
|
|
|
|
git bisect start &&
|
|
|
|
git bisect good $HASH1 || return 1
|
|
|
|
|
|
|
|
if git bisect next
|
|
|
|
then
|
|
|
|
echo Oops, should have failed.
|
|
|
|
false
|
|
|
|
else
|
|
|
|
:
|
|
|
|
fi
|
|
|
|
'
|
|
|
|
|
|
|
|
test_expect_success 'bisect start with one bad and good' '
|
|
|
|
git bisect reset &&
|
|
|
|
git bisect start &&
|
|
|
|
git bisect good $HASH1 &&
|
|
|
|
git bisect bad $HASH4 &&
|
|
|
|
git bisect next
|
|
|
|
'
|
|
|
|
|
git-bisect: make "start", "good" and "skip" succeed or fail atomically
Before this patch, when "git bisect start", "git bisect good" or
"git bisect skip" were called with many revisions, they could fail
after having already marked some revisions as "good", "bad" or
"skip".
This could be especilally bad for "git bisect start" because as
the file ".git/BISECT_NAMES" would not have been written, there
would have been no attempt to clear the marked revisions on a
"git bisect reset". That's because if there is no
".git/BISECT_NAMES" file, nothing is done to clean things up, as
the bisect session is not supposed to have started.
While at it, let's also create the ".git/BISECT_START" file, only
after ".git/BISECT_NAMES" as been created.
Signed-off-by: Christian Couder <chriscool@tuxfamily.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2008-04-14 11:41:45 +08:00
|
|
|
test_expect_success 'bisect fails if given any junk instead of revs' '
|
2008-04-12 13:53:59 +08:00
|
|
|
git bisect reset &&
|
git-bisect: make "start", "good" and "skip" succeed or fail atomically
Before this patch, when "git bisect start", "git bisect good" or
"git bisect skip" were called with many revisions, they could fail
after having already marked some revisions as "good", "bad" or
"skip".
This could be especilally bad for "git bisect start" because as
the file ".git/BISECT_NAMES" would not have been written, there
would have been no attempt to clear the marked revisions on a
"git bisect reset". That's because if there is no
".git/BISECT_NAMES" file, nothing is done to clean things up, as
the bisect session is not supposed to have started.
While at it, let's also create the ".git/BISECT_START" file, only
after ".git/BISECT_NAMES" as been created.
Signed-off-by: Christian Couder <chriscool@tuxfamily.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2008-04-14 11:41:45 +08:00
|
|
|
test_must_fail git bisect start foo $HASH1 -- &&
|
|
|
|
test_must_fail git bisect start $HASH4 $HASH1 bar -- &&
|
|
|
|
test -z "$(git for-each-ref "refs/bisect/*")" &&
|
2008-07-27 12:53:30 +08:00
|
|
|
test -z "$(ls .git/BISECT_* 2>/dev/null)" &&
|
2008-04-12 13:53:59 +08:00
|
|
|
git bisect start &&
|
|
|
|
test_must_fail git bisect good foo $HASH1 &&
|
|
|
|
test_must_fail git bisect good $HASH1 bar &&
|
|
|
|
test_must_fail git bisect bad frotz &&
|
|
|
|
test_must_fail git bisect bad $HASH3 $HASH4 &&
|
|
|
|
test_must_fail git bisect skip bar $HASH3 &&
|
|
|
|
test_must_fail git bisect skip $HASH1 foo &&
|
git-bisect: make "start", "good" and "skip" succeed or fail atomically
Before this patch, when "git bisect start", "git bisect good" or
"git bisect skip" were called with many revisions, they could fail
after having already marked some revisions as "good", "bad" or
"skip".
This could be especilally bad for "git bisect start" because as
the file ".git/BISECT_NAMES" would not have been written, there
would have been no attempt to clear the marked revisions on a
"git bisect reset". That's because if there is no
".git/BISECT_NAMES" file, nothing is done to clean things up, as
the bisect session is not supposed to have started.
While at it, let's also create the ".git/BISECT_START" file, only
after ".git/BISECT_NAMES" as been created.
Signed-off-by: Christian Couder <chriscool@tuxfamily.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2008-04-14 11:41:45 +08:00
|
|
|
test -z "$(git for-each-ref "refs/bisect/*")" &&
|
2008-04-12 13:53:59 +08:00
|
|
|
git bisect good $HASH1 &&
|
|
|
|
git bisect bad $HASH4
|
2007-04-06 13:52:37 +08:00
|
|
|
'
|
|
|
|
|
2007-11-20 13:39:53 +08:00
|
|
|
test_expect_success 'bisect reset: back in the master branch' '
|
|
|
|
git bisect reset &&
|
|
|
|
echo "* master" > branch.expect &&
|
|
|
|
git branch > branch.output &&
|
|
|
|
cmp branch.expect branch.output
|
|
|
|
'
|
|
|
|
|
|
|
|
test_expect_success 'bisect reset: back in another branch' '
|
|
|
|
git checkout -b other &&
|
|
|
|
git bisect start &&
|
|
|
|
git bisect good $HASH1 &&
|
|
|
|
git bisect bad $HASH3 &&
|
|
|
|
git bisect reset &&
|
|
|
|
echo " master" > branch.expect &&
|
|
|
|
echo "* other" >> branch.expect &&
|
|
|
|
git branch > branch.output &&
|
|
|
|
cmp branch.expect branch.output
|
|
|
|
'
|
|
|
|
|
|
|
|
test_expect_success 'bisect reset when not bisecting' '
|
|
|
|
git bisect reset &&
|
|
|
|
git branch > branch.output &&
|
|
|
|
cmp branch.expect branch.output
|
|
|
|
'
|
|
|
|
|
2007-11-15 15:18:07 +08:00
|
|
|
test_expect_success 'bisect reset removes packed refs' '
|
|
|
|
git bisect reset &&
|
|
|
|
git bisect start &&
|
|
|
|
git bisect good $HASH1 &&
|
|
|
|
git bisect bad $HASH3 &&
|
|
|
|
git pack-refs --all --prune &&
|
|
|
|
git bisect next &&
|
|
|
|
git bisect reset &&
|
|
|
|
test -z "$(git for-each-ref "refs/bisect/*")" &&
|
|
|
|
test -z "$(git for-each-ref "refs/heads/bisect")"
|
|
|
|
'
|
|
|
|
|
2011-08-04 20:01:02 +08:00
|
|
|
test_expect_success 'bisect reset removes bisect state after --no-checkout' '
|
|
|
|
git bisect reset &&
|
|
|
|
git bisect start --no-checkout &&
|
|
|
|
git bisect good $HASH1 &&
|
|
|
|
git bisect bad $HASH3 &&
|
|
|
|
git bisect next &&
|
|
|
|
git bisect reset &&
|
|
|
|
test -z "$(git for-each-ref "refs/bisect/*")" &&
|
|
|
|
test -z "$(git for-each-ref "refs/heads/bisect")" &&
|
|
|
|
test -z "$(git for-each-ref "BISECT_HEAD")"
|
|
|
|
'
|
|
|
|
|
2008-05-23 06:38:46 +08:00
|
|
|
test_expect_success 'bisect start: back in good branch' '
|
|
|
|
git branch > branch.output &&
|
|
|
|
grep "* other" branch.output > /dev/null &&
|
|
|
|
git bisect start $HASH4 $HASH1 -- &&
|
|
|
|
git bisect good &&
|
|
|
|
git bisect start $HASH4 $HASH1 -- &&
|
|
|
|
git bisect bad &&
|
|
|
|
git bisect reset &&
|
|
|
|
git branch > branch.output &&
|
|
|
|
grep "* other" branch.output > /dev/null
|
|
|
|
'
|
|
|
|
|
2011-08-04 20:00:57 +08:00
|
|
|
test_expect_success 'bisect start: no ".git/BISECT_START" created if junk rev' '
|
|
|
|
git bisect reset &&
|
2008-05-23 06:38:46 +08:00
|
|
|
test_must_fail git bisect start $HASH4 foo -- &&
|
|
|
|
git branch > branch.output &&
|
|
|
|
grep "* other" branch.output > /dev/null &&
|
|
|
|
test_must_fail test -e .git/BISECT_START
|
|
|
|
'
|
|
|
|
|
2011-08-04 20:00:57 +08:00
|
|
|
test_expect_success 'bisect start: existing ".git/BISECT_START" not modified if junk rev' '
|
|
|
|
git bisect start $HASH4 $HASH1 -- &&
|
|
|
|
git bisect good &&
|
|
|
|
cp .git/BISECT_START saved &&
|
|
|
|
test_must_fail git bisect start $HASH4 foo -- &&
|
|
|
|
git branch > branch.output &&
|
2011-11-06 01:28:42 +08:00
|
|
|
test_i18ngrep "* (no branch)" branch.output > /dev/null &&
|
2011-08-04 20:00:57 +08:00
|
|
|
test_cmp saved .git/BISECT_START
|
|
|
|
'
|
2008-05-23 06:39:22 +08:00
|
|
|
test_expect_success 'bisect start: no ".git/BISECT_START" if mistaken rev' '
|
2008-05-23 06:38:46 +08:00
|
|
|
git bisect start $HASH4 $HASH1 -- &&
|
|
|
|
git bisect good &&
|
|
|
|
test_must_fail git bisect start $HASH1 $HASH4 -- &&
|
|
|
|
git branch > branch.output &&
|
|
|
|
grep "* other" branch.output > /dev/null &&
|
|
|
|
test_must_fail test -e .git/BISECT_START
|
|
|
|
'
|
|
|
|
|
2008-05-23 06:39:22 +08:00
|
|
|
test_expect_success 'bisect start: no ".git/BISECT_START" if checkout error' '
|
2008-05-23 06:38:46 +08:00
|
|
|
echo "temp stuff" > hello &&
|
|
|
|
test_must_fail git bisect start $HASH4 $HASH1 -- &&
|
|
|
|
git branch &&
|
|
|
|
git branch > branch.output &&
|
|
|
|
grep "* other" branch.output > /dev/null &&
|
|
|
|
test_must_fail test -e .git/BISECT_START &&
|
2008-05-23 06:39:22 +08:00
|
|
|
test -z "$(git for-each-ref "refs/bisect/*")" &&
|
|
|
|
git checkout HEAD hello
|
2008-05-23 06:38:46 +08:00
|
|
|
'
|
|
|
|
|
2007-10-22 13:48:36 +08:00
|
|
|
# $HASH1 is good, $HASH4 is bad, we skip $HASH3
|
|
|
|
# but $HASH2 is bad,
|
|
|
|
# so we should find $HASH2 as the first bad commit
|
|
|
|
test_expect_success 'bisect skip: successfull result' '
|
|
|
|
git bisect reset &&
|
|
|
|
git bisect start $HASH4 $HASH1 &&
|
|
|
|
git bisect skip &&
|
|
|
|
git bisect bad > my_bisect_log.txt &&
|
2009-08-26 16:38:50 +08:00
|
|
|
grep "$HASH2 is the first bad commit" my_bisect_log.txt &&
|
2007-10-22 13:48:36 +08:00
|
|
|
git bisect reset
|
|
|
|
'
|
|
|
|
|
|
|
|
# $HASH1 is good, $HASH4 is bad, we skip $HASH3 and $HASH2
|
|
|
|
# so we should not be able to tell the first bad commit
|
|
|
|
# among $HASH2, $HASH3 and $HASH4
|
|
|
|
test_expect_success 'bisect skip: cannot tell between 3 commits' '
|
|
|
|
git bisect start $HASH4 $HASH1 &&
|
|
|
|
git bisect skip || return 1
|
|
|
|
|
|
|
|
if git bisect skip > my_bisect_log.txt
|
|
|
|
then
|
|
|
|
echo Oops, should have failed.
|
|
|
|
false
|
|
|
|
else
|
|
|
|
test $? -eq 2 &&
|
|
|
|
grep "first bad commit could be any of" my_bisect_log.txt &&
|
|
|
|
! grep $HASH1 my_bisect_log.txt &&
|
|
|
|
grep $HASH2 my_bisect_log.txt &&
|
|
|
|
grep $HASH3 my_bisect_log.txt &&
|
|
|
|
grep $HASH4 my_bisect_log.txt &&
|
|
|
|
git bisect reset
|
|
|
|
fi
|
|
|
|
'
|
|
|
|
|
|
|
|
# $HASH1 is good, $HASH4 is bad, we skip $HASH3
|
|
|
|
# but $HASH2 is good,
|
|
|
|
# so we should not be able to tell the first bad commit
|
|
|
|
# among $HASH3 and $HASH4
|
|
|
|
test_expect_success 'bisect skip: cannot tell between 2 commits' '
|
|
|
|
git bisect start $HASH4 $HASH1 &&
|
|
|
|
git bisect skip || return 1
|
|
|
|
|
|
|
|
if git bisect good > my_bisect_log.txt
|
|
|
|
then
|
|
|
|
echo Oops, should have failed.
|
|
|
|
false
|
|
|
|
else
|
|
|
|
test $? -eq 2 &&
|
|
|
|
grep "first bad commit could be any of" my_bisect_log.txt &&
|
|
|
|
! grep $HASH1 my_bisect_log.txt &&
|
|
|
|
! grep $HASH2 my_bisect_log.txt &&
|
|
|
|
grep $HASH3 my_bisect_log.txt &&
|
|
|
|
grep $HASH4 my_bisect_log.txt &&
|
|
|
|
git bisect reset
|
|
|
|
fi
|
|
|
|
'
|
|
|
|
|
2009-02-27 14:31:22 +08:00
|
|
|
# $HASH1 is good, $HASH4 is both skipped and bad, we skip $HASH3
|
|
|
|
# and $HASH2 is good,
|
|
|
|
# so we should not be able to tell the first bad commit
|
|
|
|
# among $HASH3 and $HASH4
|
|
|
|
test_expect_success 'bisect skip: with commit both bad and skipped' '
|
|
|
|
git bisect start &&
|
|
|
|
git bisect skip &&
|
|
|
|
git bisect bad &&
|
|
|
|
git bisect good $HASH1 &&
|
|
|
|
git bisect skip &&
|
|
|
|
if git bisect good > my_bisect_log.txt
|
|
|
|
then
|
|
|
|
echo Oops, should have failed.
|
|
|
|
false
|
|
|
|
else
|
|
|
|
test $? -eq 2 &&
|
|
|
|
grep "first bad commit could be any of" my_bisect_log.txt &&
|
2007-10-22 13:48:36 +08:00
|
|
|
! grep $HASH1 my_bisect_log.txt &&
|
|
|
|
! grep $HASH2 my_bisect_log.txt &&
|
|
|
|
grep $HASH3 my_bisect_log.txt &&
|
|
|
|
grep $HASH4 my_bisect_log.txt &&
|
|
|
|
git bisect reset
|
|
|
|
fi
|
|
|
|
'
|
|
|
|
|
2007-03-23 15:49:59 +08:00
|
|
|
# We want to automatically find the commit that
|
|
|
|
# introduced "Another" into hello.
|
|
|
|
test_expect_success \
|
2007-04-04 13:12:02 +08:00
|
|
|
'"git bisect run" simple case' \
|
|
|
|
'echo "#"\!"/bin/sh" > test_script.sh &&
|
2007-03-23 15:49:59 +08:00
|
|
|
echo "grep Another hello > /dev/null" >> test_script.sh &&
|
|
|
|
echo "test \$? -ne 0" >> test_script.sh &&
|
|
|
|
chmod +x test_script.sh &&
|
|
|
|
git bisect start &&
|
|
|
|
git bisect good $HASH1 &&
|
|
|
|
git bisect bad $HASH4 &&
|
|
|
|
git bisect run ./test_script.sh > my_bisect_log.txt &&
|
2009-08-26 16:38:50 +08:00
|
|
|
grep "$HASH3 is the first bad commit" my_bisect_log.txt &&
|
2007-04-04 13:12:02 +08:00
|
|
|
git bisect reset'
|
|
|
|
|
|
|
|
# We want to automatically find the commit that
|
|
|
|
# introduced "Ciao" into hello.
|
|
|
|
test_expect_success \
|
|
|
|
'"git bisect run" with more complex "git bisect start"' \
|
|
|
|
'echo "#"\!"/bin/sh" > test_script.sh &&
|
|
|
|
echo "grep Ciao hello > /dev/null" >> test_script.sh &&
|
|
|
|
echo "test \$? -ne 0" >> test_script.sh &&
|
|
|
|
chmod +x test_script.sh &&
|
|
|
|
git bisect start $HASH4 $HASH1 &&
|
|
|
|
git bisect run ./test_script.sh > my_bisect_log.txt &&
|
2009-08-26 16:38:50 +08:00
|
|
|
grep "$HASH4 is the first bad commit" my_bisect_log.txt &&
|
2007-04-04 13:12:02 +08:00
|
|
|
git bisect reset'
|
2007-03-23 15:49:59 +08:00
|
|
|
|
2007-10-22 13:48:36 +08:00
|
|
|
# $HASH1 is good, $HASH5 is bad, we skip $HASH3
|
|
|
|
# but $HASH4 is good,
|
|
|
|
# so we should find $HASH5 as the first bad commit
|
|
|
|
HASH5=
|
|
|
|
test_expect_success 'bisect skip: add line and then a new test' '
|
|
|
|
add_line_into_file "5: Another new line." hello &&
|
|
|
|
HASH5=$(git rev-parse --verify HEAD) &&
|
|
|
|
git bisect start $HASH5 $HASH1 &&
|
|
|
|
git bisect skip &&
|
|
|
|
git bisect good > my_bisect_log.txt &&
|
2009-08-26 16:38:50 +08:00
|
|
|
grep "$HASH5 is the first bad commit" my_bisect_log.txt &&
|
2007-11-20 13:39:53 +08:00
|
|
|
git bisect log > log_to_replay.txt &&
|
2007-10-22 13:49:39 +08:00
|
|
|
git bisect reset
|
|
|
|
'
|
|
|
|
|
|
|
|
test_expect_success 'bisect skip and bisect replay' '
|
|
|
|
git bisect replay log_to_replay.txt > my_bisect_log.txt &&
|
2009-08-26 16:38:50 +08:00
|
|
|
grep "$HASH5 is the first bad commit" my_bisect_log.txt &&
|
2007-10-22 13:48:36 +08:00
|
|
|
git bisect reset
|
|
|
|
'
|
|
|
|
|
2007-10-26 11:39:37 +08:00
|
|
|
HASH6=
|
|
|
|
test_expect_success 'bisect run & skip: cannot tell between 2' '
|
|
|
|
add_line_into_file "6: Yet a line." hello &&
|
|
|
|
HASH6=$(git rev-parse --verify HEAD) &&
|
|
|
|
echo "#"\!"/bin/sh" > test_script.sh &&
|
2008-03-13 05:34:34 +08:00
|
|
|
echo "sed -ne \\\$p hello | grep Ciao > /dev/null && exit 125" >> test_script.sh &&
|
2007-10-26 11:39:37 +08:00
|
|
|
echo "grep line hello > /dev/null" >> test_script.sh &&
|
|
|
|
echo "test \$? -ne 0" >> test_script.sh &&
|
|
|
|
chmod +x test_script.sh &&
|
|
|
|
git bisect start $HASH6 $HASH1 &&
|
|
|
|
if git bisect run ./test_script.sh > my_bisect_log.txt
|
|
|
|
then
|
|
|
|
echo Oops, should have failed.
|
|
|
|
false
|
|
|
|
else
|
|
|
|
test $? -eq 2 &&
|
|
|
|
grep "first bad commit could be any of" my_bisect_log.txt &&
|
|
|
|
! grep $HASH3 my_bisect_log.txt &&
|
|
|
|
! grep $HASH6 my_bisect_log.txt &&
|
|
|
|
grep $HASH4 my_bisect_log.txt &&
|
|
|
|
grep $HASH5 my_bisect_log.txt
|
|
|
|
fi
|
|
|
|
'
|
|
|
|
|
|
|
|
HASH7=
|
|
|
|
test_expect_success 'bisect run & skip: find first bad' '
|
|
|
|
git bisect reset &&
|
|
|
|
add_line_into_file "7: Should be the last line." hello &&
|
|
|
|
HASH7=$(git rev-parse --verify HEAD) &&
|
|
|
|
echo "#"\!"/bin/sh" > test_script.sh &&
|
2008-03-13 05:34:34 +08:00
|
|
|
echo "sed -ne \\\$p hello | grep Ciao > /dev/null && exit 125" >> test_script.sh &&
|
|
|
|
echo "sed -ne \\\$p hello | grep day > /dev/null && exit 125" >> test_script.sh &&
|
2007-10-26 11:39:37 +08:00
|
|
|
echo "grep Yet hello > /dev/null" >> test_script.sh &&
|
|
|
|
echo "test \$? -ne 0" >> test_script.sh &&
|
|
|
|
chmod +x test_script.sh &&
|
|
|
|
git bisect start $HASH7 $HASH1 &&
|
|
|
|
git bisect run ./test_script.sh > my_bisect_log.txt &&
|
2009-08-26 16:38:50 +08:00
|
|
|
grep "$HASH6 is the first bad commit" my_bisect_log.txt
|
2007-10-26 11:39:37 +08:00
|
|
|
'
|
|
|
|
|
2008-12-02 21:53:47 +08:00
|
|
|
test_expect_success 'bisect skip only one range' '
|
|
|
|
git bisect reset &&
|
|
|
|
git bisect start $HASH7 $HASH1 &&
|
|
|
|
git bisect skip $HASH1..$HASH5 &&
|
|
|
|
test "$HASH6" = "$(git rev-parse --verify HEAD)" &&
|
|
|
|
test_must_fail git bisect bad > my_bisect_log.txt &&
|
|
|
|
grep "first bad commit could be any of" my_bisect_log.txt
|
|
|
|
'
|
2008-02-10 21:59:50 +08:00
|
|
|
|
2008-12-02 21:53:47 +08:00
|
|
|
test_expect_success 'bisect skip many ranges' '
|
|
|
|
git bisect start $HASH7 $HASH1 &&
|
|
|
|
test "$HASH4" = "$(git rev-parse --verify HEAD)" &&
|
|
|
|
git bisect skip $HASH2 $HASH2.. ..$HASH5 &&
|
|
|
|
test "$HASH6" = "$(git rev-parse --verify HEAD)" &&
|
|
|
|
test_must_fail git bisect bad > my_bisect_log.txt &&
|
|
|
|
grep "first bad commit could be any of" my_bisect_log.txt
|
|
|
|
'
|
|
|
|
|
|
|
|
test_expect_success 'bisect starting with a detached HEAD' '
|
2008-02-10 21:59:50 +08:00
|
|
|
git bisect reset &&
|
|
|
|
git checkout master^ &&
|
|
|
|
HEAD=$(git rev-parse --verify HEAD) &&
|
|
|
|
git bisect start &&
|
2008-02-24 09:14:17 +08:00
|
|
|
test $HEAD = $(cat .git/BISECT_START) &&
|
2008-02-10 21:59:50 +08:00
|
|
|
git bisect reset &&
|
|
|
|
test $HEAD = $(git rev-parse --verify HEAD)
|
2008-05-05 15:43:00 +08:00
|
|
|
'
|
|
|
|
|
2008-05-08 05:54:28 +08:00
|
|
|
test_expect_success 'bisect errors out if bad and good are mistaken' '
|
|
|
|
git bisect reset &&
|
|
|
|
test_must_fail git bisect start $HASH2 $HASH4 2> rev_list_error &&
|
|
|
|
grep "mistake good and bad" rev_list_error &&
|
|
|
|
git bisect reset
|
|
|
|
'
|
|
|
|
|
2008-05-23 07:28:57 +08:00
|
|
|
test_expect_success 'bisect does not create a "bisect" branch' '
|
|
|
|
git bisect reset &&
|
|
|
|
git bisect start $HASH7 $HASH1 &&
|
|
|
|
git branch bisect &&
|
|
|
|
rev_hash4=$(git rev-parse --verify HEAD) &&
|
|
|
|
test "$rev_hash4" = "$HASH4" &&
|
|
|
|
git branch -D bisect &&
|
|
|
|
git bisect good &&
|
|
|
|
git branch bisect &&
|
|
|
|
rev_hash6=$(git rev-parse --verify HEAD) &&
|
|
|
|
test "$rev_hash6" = "$HASH6" &&
|
|
|
|
git bisect good > my_bisect_log.txt &&
|
2009-08-26 16:38:50 +08:00
|
|
|
grep "$HASH7 is the first bad commit" my_bisect_log.txt &&
|
2008-05-23 07:28:57 +08:00
|
|
|
git bisect reset &&
|
|
|
|
rev_hash6=$(git rev-parse --verify bisect) &&
|
|
|
|
test "$rev_hash6" = "$HASH6" &&
|
|
|
|
git branch -D bisect
|
|
|
|
'
|
|
|
|
|
bisect: test merge base if good rev is not an ancestor of bad rev
Before this patch, "git bisect", when it was given some good revs that
are not ancestor of the bad rev, didn't check if the merge bases were
good. "git bisect" just supposed that the user knew what he was doing,
and that, when he said the revs were good, he knew that it meant that
all the revs in the history leading to the good revs were also
considered good.
But in pratice, the user may not know that a good rev is not an
ancestor of the bad rev, or he may not know/remember that all revs
leading to the good rev will be considered good. So he may give a good
rev that is a sibling, instead of an ancestor, of the bad rev, when in
fact there can be one rev becoming good in the branch of the good rev
(because the bug was already fixed there, for example) instead of one
rev becoming bad in the branch of the bad rev.
For example, if there is the following history:
A--B--C--D
\
E--F
and we launch "git bisect start D F" then only C and D would have been
considered as possible first bad commit before this patch. This could
invite user errors; F could be the commit that fixes the bug that exists
everywhere else.
The purpose of this patch is to detect when "git bisect" is passed
some good revs that are not ancestors of the bad rev, and then to first
ask the user to test the merge bases between the good and bad revs.
If the merge bases are good then all is fine, we can continue
bisecting. Otherwise, if one merge base is bad, it means that the
assumption that all revs leading to the good one are good too is
wrong and we error out. In the case where one merge base is skipped we
issue a warning and then continue bisecting anyway.
These checks will also catch the case where good and bad have been
mistaken. This means that we can remove the check that was done latter
on the output of "git rev-list --bisect-vars".
Signed-off-by: Christian Couder <chriscool@tuxfamily.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2008-08-22 11:52:22 +08:00
|
|
|
# This creates a "side" branch to test "siblings" cases.
|
|
|
|
#
|
|
|
|
# H1-H2-H3-H4-H5-H6-H7 <--other
|
|
|
|
# \
|
|
|
|
# S5-S6-S7 <--side
|
|
|
|
#
|
|
|
|
test_expect_success 'side branch creation' '
|
|
|
|
git bisect reset &&
|
|
|
|
git checkout -b side $HASH4 &&
|
|
|
|
add_line_into_file "5(side): first line on a side branch" hello2 &&
|
|
|
|
SIDE_HASH5=$(git rev-parse --verify HEAD) &&
|
|
|
|
add_line_into_file "6(side): second line on a side branch" hello2 &&
|
|
|
|
SIDE_HASH6=$(git rev-parse --verify HEAD) &&
|
|
|
|
add_line_into_file "7(side): third line on a side branch" hello2 &&
|
|
|
|
SIDE_HASH7=$(git rev-parse --verify HEAD)
|
|
|
|
'
|
|
|
|
|
|
|
|
test_expect_success 'good merge base when good and bad are siblings' '
|
|
|
|
git bisect start "$HASH7" "$SIDE_HASH7" > my_bisect_log.txt &&
|
|
|
|
grep "merge base must be tested" my_bisect_log.txt &&
|
|
|
|
grep $HASH4 my_bisect_log.txt &&
|
|
|
|
git bisect good > my_bisect_log.txt &&
|
|
|
|
test_must_fail grep "merge base must be tested" my_bisect_log.txt &&
|
|
|
|
grep $HASH6 my_bisect_log.txt &&
|
|
|
|
git bisect reset
|
|
|
|
'
|
|
|
|
test_expect_success 'skipped merge base when good and bad are siblings' '
|
|
|
|
git bisect start "$SIDE_HASH7" "$HASH7" > my_bisect_log.txt &&
|
|
|
|
grep "merge base must be tested" my_bisect_log.txt &&
|
|
|
|
grep $HASH4 my_bisect_log.txt &&
|
|
|
|
git bisect skip > my_bisect_log.txt 2>&1 &&
|
2010-01-04 00:20:30 +08:00
|
|
|
grep "warning" my_bisect_log.txt &&
|
bisect: test merge base if good rev is not an ancestor of bad rev
Before this patch, "git bisect", when it was given some good revs that
are not ancestor of the bad rev, didn't check if the merge bases were
good. "git bisect" just supposed that the user knew what he was doing,
and that, when he said the revs were good, he knew that it meant that
all the revs in the history leading to the good revs were also
considered good.
But in pratice, the user may not know that a good rev is not an
ancestor of the bad rev, or he may not know/remember that all revs
leading to the good rev will be considered good. So he may give a good
rev that is a sibling, instead of an ancestor, of the bad rev, when in
fact there can be one rev becoming good in the branch of the good rev
(because the bug was already fixed there, for example) instead of one
rev becoming bad in the branch of the bad rev.
For example, if there is the following history:
A--B--C--D
\
E--F
and we launch "git bisect start D F" then only C and D would have been
considered as possible first bad commit before this patch. This could
invite user errors; F could be the commit that fixes the bug that exists
everywhere else.
The purpose of this patch is to detect when "git bisect" is passed
some good revs that are not ancestors of the bad rev, and then to first
ask the user to test the merge bases between the good and bad revs.
If the merge bases are good then all is fine, we can continue
bisecting. Otherwise, if one merge base is bad, it means that the
assumption that all revs leading to the good one are good too is
wrong and we error out. In the case where one merge base is skipped we
issue a warning and then continue bisecting anyway.
These checks will also catch the case where good and bad have been
mistaken. This means that we can remove the check that was done latter
on the output of "git rev-list --bisect-vars".
Signed-off-by: Christian Couder <chriscool@tuxfamily.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2008-08-22 11:52:22 +08:00
|
|
|
grep $SIDE_HASH6 my_bisect_log.txt &&
|
|
|
|
git bisect reset
|
|
|
|
'
|
|
|
|
|
|
|
|
test_expect_success 'bad merge base when good and bad are siblings' '
|
|
|
|
git bisect start "$HASH7" HEAD > my_bisect_log.txt &&
|
|
|
|
grep "merge base must be tested" my_bisect_log.txt &&
|
|
|
|
grep $HASH4 my_bisect_log.txt &&
|
|
|
|
test_must_fail git bisect bad > my_bisect_log.txt 2>&1 &&
|
|
|
|
grep "merge base $HASH4 is bad" my_bisect_log.txt &&
|
|
|
|
grep "fixed between $HASH4 and \[$SIDE_HASH7\]" my_bisect_log.txt &&
|
|
|
|
git bisect reset
|
|
|
|
'
|
|
|
|
|
|
|
|
# This creates a few more commits (A and B) to test "siblings" cases
|
|
|
|
# when a good and a bad rev have many merge bases.
|
|
|
|
#
|
|
|
|
# We should have the following:
|
|
|
|
#
|
|
|
|
# H1-H2-H3-H4-H5-H6-H7
|
|
|
|
# \ \ \
|
|
|
|
# S5-A \
|
|
|
|
# \ \
|
|
|
|
# S6-S7----B
|
|
|
|
#
|
|
|
|
# And there A and B have 2 merge bases (S5 and H5) that should be
|
|
|
|
# reported by "git merge-base --all A B".
|
|
|
|
#
|
|
|
|
test_expect_success 'many merge bases creation' '
|
|
|
|
git checkout "$SIDE_HASH5" &&
|
|
|
|
git merge -m "merge HASH5 and SIDE_HASH5" "$HASH5" &&
|
|
|
|
A_HASH=$(git rev-parse --verify HEAD) &&
|
|
|
|
git checkout side &&
|
|
|
|
git merge -m "merge HASH7 and SIDE_HASH7" "$HASH7" &&
|
|
|
|
B_HASH=$(git rev-parse --verify HEAD) &&
|
|
|
|
git merge-base --all "$A_HASH" "$B_HASH" > merge_bases.txt &&
|
2012-04-11 19:24:01 +08:00
|
|
|
test_line_count = 2 merge_bases.txt &&
|
bisect: test merge base if good rev is not an ancestor of bad rev
Before this patch, "git bisect", when it was given some good revs that
are not ancestor of the bad rev, didn't check if the merge bases were
good. "git bisect" just supposed that the user knew what he was doing,
and that, when he said the revs were good, he knew that it meant that
all the revs in the history leading to the good revs were also
considered good.
But in pratice, the user may not know that a good rev is not an
ancestor of the bad rev, or he may not know/remember that all revs
leading to the good rev will be considered good. So he may give a good
rev that is a sibling, instead of an ancestor, of the bad rev, when in
fact there can be one rev becoming good in the branch of the good rev
(because the bug was already fixed there, for example) instead of one
rev becoming bad in the branch of the bad rev.
For example, if there is the following history:
A--B--C--D
\
E--F
and we launch "git bisect start D F" then only C and D would have been
considered as possible first bad commit before this patch. This could
invite user errors; F could be the commit that fixes the bug that exists
everywhere else.
The purpose of this patch is to detect when "git bisect" is passed
some good revs that are not ancestors of the bad rev, and then to first
ask the user to test the merge bases between the good and bad revs.
If the merge bases are good then all is fine, we can continue
bisecting. Otherwise, if one merge base is bad, it means that the
assumption that all revs leading to the good one are good too is
wrong and we error out. In the case where one merge base is skipped we
issue a warning and then continue bisecting anyway.
These checks will also catch the case where good and bad have been
mistaken. This means that we can remove the check that was done latter
on the output of "git rev-list --bisect-vars".
Signed-off-by: Christian Couder <chriscool@tuxfamily.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2008-08-22 11:52:22 +08:00
|
|
|
grep "$HASH5" merge_bases.txt &&
|
|
|
|
grep "$SIDE_HASH5" merge_bases.txt
|
|
|
|
'
|
|
|
|
|
|
|
|
test_expect_success 'good merge bases when good and bad are siblings' '
|
|
|
|
git bisect start "$B_HASH" "$A_HASH" > my_bisect_log.txt &&
|
|
|
|
grep "merge base must be tested" my_bisect_log.txt &&
|
|
|
|
git bisect good > my_bisect_log2.txt &&
|
|
|
|
grep "merge base must be tested" my_bisect_log2.txt &&
|
|
|
|
{
|
|
|
|
{
|
|
|
|
grep "$SIDE_HASH5" my_bisect_log.txt &&
|
|
|
|
grep "$HASH5" my_bisect_log2.txt
|
|
|
|
} || {
|
|
|
|
grep "$SIDE_HASH5" my_bisect_log2.txt &&
|
|
|
|
grep "$HASH5" my_bisect_log.txt
|
|
|
|
}
|
|
|
|
} &&
|
|
|
|
git bisect reset
|
|
|
|
'
|
|
|
|
|
2008-08-22 11:52:29 +08:00
|
|
|
test_expect_success 'optimized merge base checks' '
|
|
|
|
git bisect start "$HASH7" "$SIDE_HASH7" > my_bisect_log.txt &&
|
|
|
|
grep "merge base must be tested" my_bisect_log.txt &&
|
|
|
|
grep "$HASH4" my_bisect_log.txt &&
|
|
|
|
git bisect good > my_bisect_log2.txt &&
|
|
|
|
test -f ".git/BISECT_ANCESTORS_OK" &&
|
|
|
|
test "$HASH6" = $(git rev-parse --verify HEAD) &&
|
|
|
|
git bisect bad > my_bisect_log3.txt &&
|
|
|
|
git bisect good "$A_HASH" > my_bisect_log4.txt &&
|
|
|
|
grep "merge base must be tested" my_bisect_log4.txt &&
|
2009-05-17 23:36:46 +08:00
|
|
|
test_must_fail test -f ".git/BISECT_ANCESTORS_OK"
|
2008-08-22 11:52:29 +08:00
|
|
|
'
|
|
|
|
|
2009-03-29 17:45:01 +08:00
|
|
|
# This creates another side branch called "parallel" with some files
|
|
|
|
# in some directories, to test bisecting with paths.
|
|
|
|
#
|
|
|
|
# We should have the following:
|
|
|
|
#
|
|
|
|
# P1-P2-P3-P4-P5-P6-P7
|
|
|
|
# / / /
|
|
|
|
# H1-H2-H3-H4-H5-H6-H7
|
|
|
|
# \ \ \
|
|
|
|
# S5-A \
|
|
|
|
# \ \
|
|
|
|
# S6-S7----B
|
|
|
|
#
|
|
|
|
test_expect_success '"parallel" side branch creation' '
|
|
|
|
git bisect reset &&
|
|
|
|
git checkout -b parallel $HASH1 &&
|
|
|
|
mkdir dir1 dir2 &&
|
|
|
|
add_line_into_file "1(para): line 1 on parallel branch" dir1/file1 &&
|
|
|
|
PARA_HASH1=$(git rev-parse --verify HEAD) &&
|
|
|
|
add_line_into_file "2(para): line 2 on parallel branch" dir2/file2 &&
|
|
|
|
PARA_HASH2=$(git rev-parse --verify HEAD) &&
|
|
|
|
add_line_into_file "3(para): line 3 on parallel branch" dir2/file3 &&
|
2010-10-31 09:46:54 +08:00
|
|
|
PARA_HASH3=$(git rev-parse --verify HEAD) &&
|
2009-03-29 17:45:01 +08:00
|
|
|
git merge -m "merge HASH4 and PARA_HASH3" "$HASH4" &&
|
2010-10-31 09:46:54 +08:00
|
|
|
PARA_HASH4=$(git rev-parse --verify HEAD) &&
|
2009-03-29 17:45:01 +08:00
|
|
|
add_line_into_file "5(para): add line on parallel branch" dir1/file1 &&
|
2010-10-31 09:46:54 +08:00
|
|
|
PARA_HASH5=$(git rev-parse --verify HEAD) &&
|
2009-03-29 17:45:01 +08:00
|
|
|
add_line_into_file "6(para): add line on parallel branch" dir2/file2 &&
|
2010-10-31 09:46:54 +08:00
|
|
|
PARA_HASH6=$(git rev-parse --verify HEAD) &&
|
2009-03-29 17:45:01 +08:00
|
|
|
git merge -m "merge HASH7 and PARA_HASH6" "$HASH7" &&
|
|
|
|
PARA_HASH7=$(git rev-parse --verify HEAD)
|
|
|
|
'
|
|
|
|
|
|
|
|
test_expect_success 'restricting bisection on one dir' '
|
|
|
|
git bisect reset &&
|
|
|
|
git bisect start HEAD $HASH1 -- dir1 &&
|
|
|
|
para1=$(git rev-parse --verify HEAD) &&
|
|
|
|
test "$para1" = "$PARA_HASH1" &&
|
|
|
|
git bisect bad > my_bisect_log.txt &&
|
2009-08-26 16:38:50 +08:00
|
|
|
grep "$PARA_HASH1 is the first bad commit" my_bisect_log.txt
|
2009-03-29 17:45:01 +08:00
|
|
|
'
|
|
|
|
|
|
|
|
test_expect_success 'restricting bisection on one dir and a file' '
|
|
|
|
git bisect reset &&
|
|
|
|
git bisect start HEAD $HASH1 -- dir1 hello &&
|
|
|
|
para4=$(git rev-parse --verify HEAD) &&
|
|
|
|
test "$para4" = "$PARA_HASH4" &&
|
|
|
|
git bisect bad &&
|
|
|
|
hash3=$(git rev-parse --verify HEAD) &&
|
|
|
|
test "$hash3" = "$HASH3" &&
|
|
|
|
git bisect good &&
|
|
|
|
hash4=$(git rev-parse --verify HEAD) &&
|
|
|
|
test "$hash4" = "$HASH4" &&
|
|
|
|
git bisect good &&
|
|
|
|
para1=$(git rev-parse --verify HEAD) &&
|
|
|
|
test "$para1" = "$PARA_HASH1" &&
|
|
|
|
git bisect good > my_bisect_log.txt &&
|
2009-08-26 16:38:50 +08:00
|
|
|
grep "$PARA_HASH4 is the first bad commit" my_bisect_log.txt
|
2009-03-29 17:45:01 +08:00
|
|
|
'
|
|
|
|
|
2009-06-06 12:41:35 +08:00
|
|
|
test_expect_success 'skipping away from skipped commit' '
|
|
|
|
git bisect start $PARA_HASH7 $HASH1 &&
|
|
|
|
para4=$(git rev-parse --verify HEAD) &&
|
|
|
|
test "$para4" = "$PARA_HASH4" &&
|
|
|
|
git bisect skip &&
|
|
|
|
hash7=$(git rev-parse --verify HEAD) &&
|
|
|
|
test "$hash7" = "$HASH7" &&
|
|
|
|
git bisect skip &&
|
2009-06-13 13:21:06 +08:00
|
|
|
para3=$(git rev-parse --verify HEAD) &&
|
|
|
|
test "$para3" = "$PARA_HASH3"
|
2009-06-06 12:41:35 +08:00
|
|
|
'
|
|
|
|
|
2010-03-01 06:19:09 +08:00
|
|
|
test_expect_success 'erroring out when using bad path parameters' '
|
|
|
|
test_must_fail git bisect start $PARA_HASH7 $HASH1 -- foobar 2> error.txt &&
|
|
|
|
grep "bad path parameters" error.txt
|
|
|
|
'
|
|
|
|
|
2011-08-09 10:11:54 +08:00
|
|
|
test_expect_success 'test bisection on bare repo - --no-checkout specified' '
|
|
|
|
git clone --bare . bare.nocheckout &&
|
|
|
|
(
|
|
|
|
cd bare.nocheckout &&
|
|
|
|
git bisect start --no-checkout &&
|
|
|
|
git bisect good $HASH1 &&
|
|
|
|
git bisect bad $HASH4 &&
|
|
|
|
git bisect run eval \
|
|
|
|
"test \$(git rev-list BISECT_HEAD ^$HASH2 --max-count=1 | wc -l) = 0" \
|
|
|
|
>../nocheckout.log &&
|
|
|
|
git bisect reset
|
|
|
|
) &&
|
|
|
|
grep "$HASH3 is the first bad commit" nocheckout.log
|
|
|
|
'
|
|
|
|
|
|
|
|
|
|
|
|
test_expect_success 'test bisection on bare repo - --no-checkout defaulted' '
|
|
|
|
git clone --bare . bare.defaulted &&
|
|
|
|
(
|
|
|
|
cd bare.defaulted &&
|
|
|
|
git bisect start &&
|
|
|
|
git bisect good $HASH1 &&
|
|
|
|
git bisect bad $HASH4 &&
|
|
|
|
git bisect run eval \
|
|
|
|
"test \$(git rev-list BISECT_HEAD ^$HASH2 --max-count=1 | wc -l) = 0" \
|
|
|
|
>../defaulted.log &&
|
|
|
|
git bisect reset
|
|
|
|
) &&
|
|
|
|
grep "$HASH3 is the first bad commit" defaulted.log
|
|
|
|
'
|
|
|
|
|
2007-03-23 15:49:59 +08:00
|
|
|
#
|
2011-08-04 20:00:59 +08:00
|
|
|
# This creates a broken branch which cannot be checked out because
|
|
|
|
# the tree created has been deleted.
|
2007-03-23 15:49:59 +08:00
|
|
|
#
|
2011-08-04 20:00:59 +08:00
|
|
|
# H1-H2-H3-H4-H5-H6-H7 <--other
|
|
|
|
# \
|
|
|
|
# S5-S6'-S7'-S8'-S9 <--broken
|
|
|
|
#
|
|
|
|
# Commits marked with ' have a missing tree.
|
|
|
|
#
|
|
|
|
test_expect_success 'broken branch creation' '
|
|
|
|
git bisect reset &&
|
|
|
|
git checkout -b broken $HASH4 &&
|
|
|
|
git tag BROKEN_HASH4 $HASH4 &&
|
|
|
|
add_line_into_file "5(broken): first line on a broken branch" hello2 &&
|
|
|
|
git tag BROKEN_HASH5 &&
|
|
|
|
mkdir missing &&
|
|
|
|
:> missing/MISSING &&
|
|
|
|
git add missing/MISSING &&
|
|
|
|
git commit -m "6(broken): Added file that will be deleted"
|
|
|
|
git tag BROKEN_HASH6 &&
|
|
|
|
add_line_into_file "7(broken): second line on a broken branch" hello2 &&
|
|
|
|
git tag BROKEN_HASH7 &&
|
|
|
|
add_line_into_file "8(broken): third line on a broken branch" hello2 &&
|
|
|
|
git tag BROKEN_HASH8 &&
|
|
|
|
git rm missing/MISSING &&
|
|
|
|
git commit -m "9(broken): Remove missing file"
|
|
|
|
git tag BROKEN_HASH9 &&
|
|
|
|
rm .git/objects/39/f7e61a724187ab767d2e08442d9b6b9dab587d
|
|
|
|
'
|
|
|
|
|
|
|
|
echo "" > expected.ok
|
|
|
|
cat > expected.missing-tree.default <<EOF
|
|
|
|
fatal: unable to read tree 39f7e61a724187ab767d2e08442d9b6b9dab587d
|
|
|
|
EOF
|
|
|
|
|
|
|
|
test_expect_success 'bisect fails if tree is broken on start commit' '
|
|
|
|
git bisect reset &&
|
|
|
|
test_must_fail git bisect start BROKEN_HASH7 BROKEN_HASH4 2>error.txt &&
|
|
|
|
test_cmp expected.missing-tree.default error.txt
|
|
|
|
'
|
|
|
|
|
|
|
|
test_expect_success 'bisect fails if tree is broken on trial commit' '
|
|
|
|
git bisect reset &&
|
|
|
|
test_must_fail git bisect start BROKEN_HASH9 BROKEN_HASH4 2>error.txt &&
|
|
|
|
git reset --hard broken &&
|
|
|
|
git checkout broken &&
|
|
|
|
test_cmp expected.missing-tree.default error.txt
|
|
|
|
'
|
|
|
|
|
2011-08-04 20:01:02 +08:00
|
|
|
check_same()
|
|
|
|
{
|
|
|
|
echo "Checking $1 is the same as $2" &&
|
|
|
|
git rev-parse "$1" > expected.same &&
|
|
|
|
git rev-parse "$2" > expected.actual &&
|
|
|
|
test_cmp expected.same expected.actual
|
|
|
|
}
|
|
|
|
|
|
|
|
test_expect_success 'bisect: --no-checkout - start commit bad' '
|
|
|
|
git bisect reset &&
|
|
|
|
git bisect start BROKEN_HASH7 BROKEN_HASH4 --no-checkout &&
|
|
|
|
check_same BROKEN_HASH6 BISECT_HEAD &&
|
|
|
|
git bisect reset
|
|
|
|
'
|
|
|
|
|
|
|
|
test_expect_success 'bisect: --no-checkout - trial commit bad' '
|
|
|
|
git bisect reset &&
|
|
|
|
git bisect start broken BROKEN_HASH4 --no-checkout &&
|
|
|
|
check_same BROKEN_HASH6 BISECT_HEAD &&
|
|
|
|
git bisect reset
|
|
|
|
'
|
|
|
|
|
|
|
|
test_expect_success 'bisect: --no-checkout - target before breakage' '
|
|
|
|
git bisect reset &&
|
|
|
|
git bisect start broken BROKEN_HASH4 --no-checkout &&
|
|
|
|
check_same BROKEN_HASH6 BISECT_HEAD &&
|
|
|
|
git bisect bad BISECT_HEAD &&
|
|
|
|
check_same BROKEN_HASH5 BISECT_HEAD &&
|
|
|
|
git bisect bad BISECT_HEAD &&
|
|
|
|
check_same BROKEN_HASH5 bisect/bad &&
|
|
|
|
git bisect reset
|
|
|
|
'
|
|
|
|
|
|
|
|
test_expect_success 'bisect: --no-checkout - target in breakage' '
|
|
|
|
git bisect reset &&
|
|
|
|
git bisect start broken BROKEN_HASH4 --no-checkout &&
|
|
|
|
check_same BROKEN_HASH6 BISECT_HEAD &&
|
|
|
|
git bisect bad BISECT_HEAD &&
|
|
|
|
check_same BROKEN_HASH5 BISECT_HEAD &&
|
|
|
|
git bisect good BISECT_HEAD &&
|
|
|
|
check_same BROKEN_HASH6 bisect/bad &&
|
|
|
|
git bisect reset
|
|
|
|
'
|
|
|
|
|
|
|
|
test_expect_success 'bisect: --no-checkout - target after breakage' '
|
|
|
|
git bisect reset &&
|
|
|
|
git bisect start broken BROKEN_HASH4 --no-checkout &&
|
|
|
|
check_same BROKEN_HASH6 BISECT_HEAD &&
|
|
|
|
git bisect good BISECT_HEAD &&
|
|
|
|
check_same BROKEN_HASH8 BISECT_HEAD &&
|
|
|
|
git bisect good BISECT_HEAD &&
|
|
|
|
check_same BROKEN_HASH9 bisect/bad &&
|
|
|
|
git bisect reset
|
|
|
|
'
|
|
|
|
|
|
|
|
test_expect_success 'bisect: demonstrate identification of damage boundary' "
|
|
|
|
git bisect reset &&
|
|
|
|
git checkout broken &&
|
|
|
|
git bisect start broken master --no-checkout &&
|
2011-08-30 04:09:25 +08:00
|
|
|
git bisect run \"\$SHELL_PATH\" -c '
|
2011-08-04 20:01:02 +08:00
|
|
|
GOOD=\$(git for-each-ref \"--format=%(objectname)\" refs/bisect/good-*) &&
|
|
|
|
git rev-list --objects BISECT_HEAD --not \$GOOD >tmp.\$\$ &&
|
|
|
|
git pack-objects --stdout >/dev/null < tmp.\$\$
|
|
|
|
rc=\$?
|
|
|
|
rm -f tmp.\$\$
|
|
|
|
test \$rc = 0' &&
|
|
|
|
check_same BROKEN_HASH6 bisect/bad &&
|
|
|
|
git bisect reset
|
|
|
|
"
|
|
|
|
|
2007-03-23 15:49:59 +08:00
|
|
|
test_done
|