summaryrefslogtreecommitdiff
path: root/src/bin/scripts/t/080_pg_isready.pl
diff options
context:
space:
mode:
authorNoah Misch <noah@leadboat.com>2022-03-04 18:53:13 -0800
committerNoah Misch <noah@leadboat.com>2022-03-04 18:53:17 -0800
commit29ec94efd08b0b3f863db13f5978cdeab4f1c8dc (patch)
tree7c3794291cf7c2a1bf6f38a775e4d8ec767186cf /src/bin/scripts/t/080_pg_isready.pl
parent59392746cb3fd3c23b5f7bfa9568a71705ca30d1 (diff)
Introduce PG_TEST_TIMEOUT_DEFAULT for TAP suite non-elapsing timeouts.
Slow hosts may avoid load-induced, spurious failures by setting environment variable PG_TEST_TIMEOUT_DEFAULT to some number of seconds greater than 180. Developers may see faster failures by setting that environment variable to some lesser number of seconds. In tests, write $PostgreSQL::Test::Utils::timeout_default wherever the convention has been to write 180. This change raises the default for some briefer timeouts. Back-patch to v10 (all supported versions). Discussion: https://postgr.es/m/20220218052842.GA3627003@rfd.leadboat.com
Diffstat (limited to 'src/bin/scripts/t/080_pg_isready.pl')
-rw-r--r--src/bin/scripts/t/080_pg_isready.pl4
1 files changed, 2 insertions, 2 deletions
diff --git a/src/bin/scripts/t/080_pg_isready.pl b/src/bin/scripts/t/080_pg_isready.pl
index 6da89e1b04f..fc2f54f061c 100644
--- a/src/bin/scripts/t/080_pg_isready.pl
+++ b/src/bin/scripts/t/080_pg_isready.pl
@@ -15,6 +15,6 @@ my $node = get_new_node('main');
$node->init;
$node->start;
-# use a long timeout for the benefit of very slow buildfarm machines
-$node->command_ok([qw(pg_isready --timeout=60)],
+$node->command_ok(
+ [ 'pg_isready', "--timeout=$TestLib::timeout_default" ],
'succeeds with server running');