[perl-Glib/stable-1-22] Try to fix a test failure in 9.t



commit a557b9507a19389f8596d53f703fcb98f8350fea
Author: Torsten Schönfeld <kaffeetisch gmx de>
Date:   Sun May 30 15:31:57 2010 +0200

    Try to fix a test failure in 9.t
    
    The report
    <http://www.cpantesters.org/cpan/report/05025030-b19f-3f77-b713-d32bba55d77f>
    indicates that the SIGALRM test failed, i.e. the timeout handler ran
    before the SIGALRM handler.  Increase the timeout delay to 5 seconds to
    try to fix this.

 t/9.t |    6 +++---
 1 files changed, 3 insertions(+), 3 deletions(-)
---
diff --git a/t/9.t b/t/9.t
index e46e417..ed8ec85 100644
--- a/t/9.t
+++ b/t/9.t
@@ -138,7 +138,7 @@ if ($Config{archname} =~ m/^(x86_64|mipsel|mips|alpha)/
 # 1.072 fixes the long-standing "bug" that perl's safe signal handling
 # caused asynchronous signals not to be delivered while a main loop is
 # running (because control stays in C).  let's make sure that we can
-# get a 1 second alarm before a 2 second timeout has a chance to fire.
+# get a 1 second alarm before a 5 second timeout has a chance to fire.
 if ($^O eq 'MSWin32') {
 	# XXX Win32 doesn't do SIGALRM the way unix does; either the alarm
 	# doesn't interrupt the poll, or alarm just doesn't work.
@@ -152,7 +152,7 @@ if ($^O eq 'MSWin32') {
 		$loop->quit;
 	};
 	my $timeout_fired = 0;
-	Glib::Timeout->add (2000, sub {
+	Glib::Timeout->add (5000, sub {
 		$timeout_fired++;
 		$loop->quit;
 		0;
@@ -161,7 +161,7 @@ if ($^O eq 'MSWin32') {
 	$loop->run;
 	print ""
 	    . ($timeout_fired ? "not ok" : "ok")
-	    . " 16 - 1 sec alarm handler fires before 2 sec timeout\n";
+	    . " 16 - 1 sec alarm handler fires before 5 sec timeout\n";
 }
 
 if (Glib->CHECK_VERSION (2, 4, 0)) {



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]