Re: git-bisect not working correctly in the kvm.git repository?

From: walt <w41ter@gmail.com>
Date: Nov 17, 2008, 22:11 UTC
Message-ID: <alpine.LNX.2.00.0811171350540.4238@x9.ybpnyarg>
In-Reply-To: <200811172047.03669.chriscool@tuxfamily.org>

On Mon, 17 Nov 2008, Christian Couder wrote:

Show 25 quoted lines

> Le lundi 17 novembre 2008, walt a écrit :
> > I'm trying to find a bug introduced somewhere between kvm-69
> > and kvm-70, so of course I want to git-bisect down to it.
> >
> > The weirdness is that when I give git-bisect the good and
> > bad tags, almost everything in my working directory just
> > disappears, leaving only the qemu subdirectory behind.
> >
> > Can anyone else reproduce this with the kvm.git repo?
> > (I don't see this problem with the linux.git repo or the
> > git.git repo, so it seems to be something with the kvm.git
> > repo itself.)
>
> I cannot reproduce this:
>
> $ git bisect start kvm-70 kvm-69
> Bisecting: 846 revisions left to test after this
> [80bfc25f42db6d4715c7688ae2352c5a8038fe7e] ntfs: le*_add_cpu conversion
> $ find . -type f |wc -l
> 24286
> $ git bisect reset
> Previous HEAD position was 80bfc25... ntfs: le*_add_cpu conversion
> Switched to branch "master"
> $ find . -type f |wc -l
> 24384

Your numbers are so different from mine I'm wondering if we are using different repositories.

$~/src/kvm-userspace find . -type f | wc -l 1715

$~/src/kvm-userspace git bisect start kvm-70 kvm-69
Bisecting: 176 revisions left to test after this
[06508be8108f785caead849a717c9e6d67da62d7] Un-break MIPS conditional moves, by
Richard Sandiford.
wa1ter@k9:~/src/kvm-userspace find . -type f | wc -l
1413

$~/src/kvm-userspace cat .git/config
[core]
        repositoryformatversion = 0
        filemode = true
        bare = false
        logallrefupdates = true
[remote "origin"]
        url = git://git.kernel.org/pub/scm/virt/kvm/kvm-userspace.git
        fetch = +refs/heads/*:refs/remotes/origin/*
[branch "master"]
        remote = origin
        merge = refs/heads/master

I track Junio's git.git and it's current as of this morning, but I also tried git v1.5.0 (chosen at random) and got the same results. What repo are you using?

Thanks.