Git Bug Resolve: bisect run failed to locate the right commit, not git bug

Dear git developer:

On August 27, I report a bug on git bisect: "bisect run failed to locate the right commit"

Today, my friend told me that the problem may be caused by the python compiled file *.pyc. Since if python see the pyc is a "new" compiled, it will directly run *pyc file but update it.

When we use bisect-run, it quickly checkout different version and run the script to test it. It's so fast that the *pyc file are still new files, so python run *.pyc and get same result. That's the wrong result came from.

There are two way to avoid this problem: First is delete all *.pyc before python run, add a test.sh with following content: find . -name *.pyc -exec rm {} \; ./autoscript.py

Second is let python run slower, adding a delay in autoscript.py: import time time.sleep(1)

Both method let git-bisect-run give the right result.

Sorry about the wrong bug report, it prove that git-bisect-run is very very fast -- too fast to cause some mistake lol

Sincerely YodaLee 20140828