From: Noah Misch <noah@leadboat.com>
Date: Thu, 11 Feb 2016 01:34:57 +0000 (-0500)
Subject: In pg_rewind test suite, triple promote timeout to 90s.
X-Git-Tag: REL9_6_BETA1~726
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=64d89a93c0a8b2ead0503684f54784bd071adad9;p=postgresql

In pg_rewind test suite, triple promote timeout to 90s.

Thirty seconds was not consistently enough for promotion to complete on
buildfarm members sungazer and tern.  Experiments suggest 43s would have
been enough.  Back-patch to 9.5, where pg_rewind was introduced.
---

diff --git a/src/test/perl/PostgresNode.pm b/src/test/perl/PostgresNode.pm
index 6152c601bd..2ab9aee334 100644
--- a/src/test/perl/PostgresNode.pm
+++ b/src/test/perl/PostgresNode.pm
@@ -404,7 +404,7 @@ sub poll_query_until
 {
 	my ($self, $dbname, $query) = @_;
 
-	my $max_attempts = 30;
+	my $max_attempts = 90;
 	my $attempts     = 0;
 	my ($stdout, $stderr);
 
@@ -426,7 +426,7 @@ sub poll_query_until
 		$attempts++;
 	}
 
-	# The query result didn't change in 30 seconds. Give up. Print the stderr
+	# The query result didn't change in 90 seconds. Give up. Print the stderr
 	# from the last attempt, hopefully that's useful for debugging.
 	diag $stderr;
 	return 0;