{"thread":{"id":"37438","subject":"Git Bug Resolve: bisect run failed to locate the right commit, not git bug","startedAt":"2014-08-28T15:43:12Z","lastAt":"2014-08-28T15:43:12Z","messageCount":1,"participants":["李祐棠"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"248497","messageId":"C40A01C66E914D4EB90E1B40564B0E56CBFE311B@MBOX2-4.ntu.internal","threadId":"37438","inReplyTo":null,"subject":"Git Bug Resolve: bisect run failed to locate the right commit, not git bug","fromName":"李祐棠","fromEmail":"r01942008@ntu.edu.tw","sentAt":"2014-08-28T15:43:12Z","receivedAt":"2014-08-28T15:43:12Z","isPatch":false,"sender":{"key":"r01942008@ntu.edu.tw","avatar":null},"body":"Dear git developer:\n\nOn August 27, I report a bug on git bisect: \n\"bisect run failed to locate the right commit\"\n\nToday, my friend told me that the problem may be caused by the python compiled file *.pyc.\nSince if python see the pyc is a \"new\" compiled, it will directly run *pyc file but update it.\n\nWhen we use bisect-run, it quickly checkout different version and run the script to test it.\nIt's so fast that the *pyc file are still new files, so python run *.pyc and get same result.\nThat's the wrong result came from.\n\nThere are two way to avoid this problem:\nFirst is delete all *.pyc before python run, add a test.sh with following content:\nfind . -name *.pyc -exec rm {} \\;\n./autoscript.py\n\nSecond is let python run slower, adding a delay in autoscript.py:\nimport time\ntime.sleep(1)\n\nBoth method let git-bisect-run give the right result.\n\nSorry about the wrong bug report, it prove that git-bisect-run is very very fast -- too fast to cause some mistake lol\n\nSincerely \nYodaLee\n20140828"}]}