Due to a bug in dependency_unsatisfied(), tests were executed as long as the first...
authorFabian Keil <fk@fabiankeil.de>
Wed, 27 May 2009 20:45:31 +0000 (20:45 +0000)
committerFabian Keil <fk@fabiankeil.de>
Wed, 27 May 2009 20:45:31 +0000 (20:45 +0000)
It "worked" so far, because until recently we only had a single
config-line dependency and only had to check the user-manual
directive, which usually is the first one.

And there I was rewriting client_connection() from scratch,
puzzled that the stupid connection-sharing tests would still
fail.

tools/privoxy-regression-test.pl

index 0a9d379..920b218 100755 (executable)
@@ -7,7 +7,7 @@
 # A regression test "framework" for Privoxy. For documentation see:
 # perldoc privoxy-regression-test.pl
 #
-# $Id: privoxy-regression-test.pl,v 1.172 2009/05/25 19:31:42 fk Exp fk $
+# $Id: privoxy-regression-test.pl,v 1.176 2009/05/27 20:26:59 fk Exp fk $
 #
 # Wish list:
 #
@@ -587,8 +587,10 @@ sub dependency_unsatisfied ($) {
 
         foreach (@privoxy_config) {
 
-             $dependency_problem = undef if (/$dependency/);
-             last; # XXX: this looks ... interesting.
+            if (/$dependency/) {
+                $dependency_problem = undef;
+                last;
+            }
         }
 
     } elsif (defined ($dependencies{$level}{'feature status'})) {