From: Siarhei Siamashka <siarhei.siamashka@gmail.com>
Date: Wed, 6 Jun 2012 20:54:20 +0000 (+0300)
Subject: test: fix bisecting issue in fuzzer-find-diff.pl
X-Git-Tag: pixman-0.27.2~47
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=492dac7593075e622cfeddc73298df29d50b76bc;p=platform%2Fupstream%2Fpixman.git

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

diff --git a/test/fuzzer-find-diff.pl b/test/fuzzer-find-diff.pl
index 53d9b8d..e1d67fb 100755
--- a/test/fuzzer-find-diff.pl
+++ b/test/fuzzer-find-diff.pl
@@ -29,10 +29,17 @@ sub test_range {
     my $min = shift;
     my $max = shift;
 
+    # check that [$min, $max] range is "bad", otherwise return
     if (`$ARGV[0] $min $max 2>/dev/null` eq `$ARGV[1] $min $max 2>/dev/null`) {
         return;
     }
 
+    # check that $min itself is "good", otherwise return
+    if (`$ARGV[0] $min 2>/dev/null` ne `$ARGV[1] $min 2>/dev/null`) {
+        return $min;
+    }
+
+    # start bisecting
     while ($max != $min + 1) {
         my $avg = int(($min + $max) / 2);
         my $res1 = `$ARGV[0] $min $avg 2>/dev/null`;