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

1 messages from 2014-08-28 to 2014-08-28. Participants: 李祐棠.
Thread: https://gitlist.dev/t/37438

## 李祐棠, 2014-08-28 15:43

Subject: Git Bug Resolve: bisect run failed to locate the right commit, not git bug
Message-ID: <C40A01C66E914D4EB90E1B40564B0E56CBFE311B@MBOX2-4.ntu.internal>
URL: https://gitlist.dev/e/C40A01C66E914D4EB90E1B40564B0E56CBFE311B%40MBOX2-4.ntu.internal

```
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
```