From: Tom Lane Date: Sun, 1 Oct 2017 16:43:47 +0000 (-0400) Subject: Use a longer connection timeout in pg_isready test. X-Git-Tag: REL9_6_6~45 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=858e9f27be2e0344cc97592cf3c23be54cb0db2c;p=postgresql 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. --- diff --git a/src/bin/scripts/t/080_pg_isready.pl b/src/bin/scripts/t/080_pg_isready.pl index d9830b5b3a..d01804da37 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');