postgres.git / summary / log / commit / refs

commit    45ec8da100a1adcbc792025db59d3009d78da02d
Author:   Tom Lane <tgl@sss.pgh.pa.us>
Date:     Sun Oct 01 16:43:47 2017 +0000
First released in: 11.0, 9.4.15, 9.5.10, 9.6.6, 10.0

    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 f432505d5cd..2ddb03d7c24 100644
--- a/src/bin/scripts/t/080_pg_isready.pl
+++ b/src/bin/scripts/t/080_pg_isready.pl
@@ -12,4 +12,5 @@ command_fails(['pg_isready'], 'fails with no server running');
 my $tempdir = tempdir;
 start_test_server $tempdir;
 
-command_ok(['pg_isready'], 'succeeds with server running');
+# use a long timeout for the benefit of very slow buildfarm machines
+command_ok([qw(pg_isready --timeout=60)], 'succeeds with server running');


[parent: 232c7cbcbbc6]