diff options
| author | Noah Misch | 2022-03-05 02:53:13 +0000 |
|---|---|---|
| committer | Noah Misch | 2022-03-05 02:53:13 +0000 |
| commit | f2698ea02ca8a56f38935d2b300ac54936712558 (patch) | |
| tree | fa031ce71f9acf7327c3898e708682838fe210a4 /src/bin/scripts | |
| parent | 9240589798e02705dbe3e86549d064988c0f47d2 (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')
| -rw-r--r-- | src/bin/scripts/t/080_pg_isready.pl | 4 |
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 e8436dc7e8a..c45ca6666f9 100644 --- a/src/bin/scripts/t/080_pg_isready.pl +++ b/src/bin/scripts/t/080_pg_isready.pl @@ -18,8 +18,8 @@ my $node = PostgreSQL::Test::Cluster->new('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=$PostgreSQL::Test::Utils::timeout_default" ], 'succeeds with server running'); done_testing(); |