postgres.git / summary / log / commit / refs

commit    1a6b2b16565aa70f663f83aa6c47b4cbc545eeb2
Author:   Tom Lane <tgl@sss.pgh.pa.us>
Date:     Sun Oct 01 16:43:47 2017 +0000

    Use a longer connection timeout in pg_isready test.
    
    Buildfarm members skink and sungazer have both recently failed this
    test, with symptoms indicating that the default 3-second timeout
    isn't quite enough for those very slow systems.  There's no reason
    to be miserly with this timeout, so boost it to 60 seconds.
    
    Back-patch to all versions containing this test.  That may be overkill,
    because the failure has only been observed in the v10 branch, but
    I don't feel like having to revisit this later.


 src/bin/scripts/t/080_pg_isready.pl | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/src/bin/scripts/t/080_pg_isready.pl b/src/bin/scripts/t/080_pg_isready.pl
index d9830b5b3ad..d01804da371 100644
--- a/src/bin/scripts/t/080_pg_isready.pl
+++ b/src/bin/scripts/t/080_pg_isready.pl
@@ -15,4 +15,5 @@ my $node = get_new_node('main');
 $node->init;
 $node->start;
 
-$node->command_ok(['pg_isready'], 'succeeds with server running');
+# use a long timeout for the benefit of very slow buildfarm machines
+$node->command_ok([qw(pg_isready --timeout=60)], 'succeeds with server running');


[parent: e775dd6a4b1b]