commit | 87e5e9da9be525683ab25246703813bfc2140b68 | [log] [tgz] |
---|---|---|
author | Siarhei Siamashka <siarhei.siamashka@gmail.com> | Wed Jun 06 23:54:20 2012 +0300 |
committer | Matt Turner <mattst88@gmail.com> | Wed Jun 13 11:13:29 2012 -0400 |
tree | 6fdffb692cb3adc23585439da95f9b25c78d9e79 | |
parent | 71ada855cf5c25e02d779fe68dea6b2bdd5c516d [diff] |
test: fix bisecting issue in fuzzer-find-diff.pl Before bisecting to find the exact test which has failed, we first need to make sure that the first test is fine (the first test is "good" and the whole range is "bad"). Otherwise test 2 gets incorrectly flagged as problematic in the case if we already got a failure on test 1 right from the start.