diff options
| author | Noah Misch <noah@leadboat.com> | 2022-03-04 18:53:13 -0800 |
|---|---|---|
| committer | Noah Misch <noah@leadboat.com> | 2022-03-04 18:53:17 -0800 |
| commit | 7f2e1befc039029ce5be36088f6872ad393d007c (patch) | |
| tree | 726868b0193f75553dd1c35f80451c257ba596d8 /src/bin/scripts/t | |
| parent | 18c04d1574568fd68e4f498483f3b10b11018c68 (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')
| -rw-r--r-- | src/bin/scripts/t/080_pg_isready.pl | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/src/bin/scripts/t/080_pg_isready.pl b/src/bin/scripts/t/080_pg_isready.pl index d01804da371..fc2f54f061c 100644 --- a/src/bin/scripts/t/080_pg_isready.pl +++ b/src/bin/scripts/t/080_pg_isready.pl @@ -15,5 +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)], 'succeeds with server running'); +$node->command_ok( + [ 'pg_isready', "--timeout=$TestLib::timeout_default" ], + 'succeeds with server running'); |