Re: bisect gives strange answer
- From
- Sanjoy Mahajan <sanjoy@mrao.cam.ac.uk>
- Date
- Aug 5, 2005, 15:38 UTC
- Message-ID
- <E1E14Hj-0001Nt-00@skye.ra.phy.cam.ac.uk>
- In-Reply-To
- <20050804192838.GB26714@mars.ravnborg.org>
> If you see any sort of evidence that this would hold true I really like > to know.
I haven't found any evidence. When I rebuilt the kernels from scratch (exporting them into an empty directory using cg-export), I got reliable data and bisected down to a patch that probably was a problem.
I will redo those tests but rebuilding in place after each bisection (with -f added to all the git checkout uses in git-bisect-script) and see whether I get the same results. If I don't, it could be due to git or git-bisect (but not so likely with the -f switch) or to the build system. Will keep you and Junio posted.
-Sanjoy