agora inbox for [email protected]help / color / mirror / Atom feed
[PATCH v2 3/7] Row pattern recognition patch (planner). 573+ messages / 2 participants [nested] [flat]
* [PATCH v2 3/7] Row pattern recognition patch (planner). @ 2023-06-26 08:05 Tatsuo Ishii <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Tatsuo Ishii @ 2023-06-26 08:05 UTC (permalink / raw) --- src/backend/optimizer/plan/createplan.c | 19 ++++++++++++++----- src/include/nodes/plannodes.h | 12 ++++++++++++ 2 files changed, 26 insertions(+), 5 deletions(-) diff --git a/src/backend/optimizer/plan/createplan.c b/src/backend/optimizer/plan/createplan.c index 4bb38160b3..c10ac65a4c 100644 --- a/src/backend/optimizer/plan/createplan.c +++ b/src/backend/optimizer/plan/createplan.c @@ -286,9 +286,9 @@ static WindowAgg *make_windowagg(List *tlist, Index winref, int ordNumCols, AttrNumber *ordColIdx, Oid *ordOperators, Oid *ordCollations, int frameOptions, Node *startOffset, Node *endOffset, Oid startInRangeFunc, Oid endInRangeFunc, - Oid inRangeColl, bool inRangeAsc, bool inRangeNullsFirst, - List *runCondition, List *qual, bool topWindow, - Plan *lefttree); + Oid inRangeColl, bool inRangeAsc, bool inRangeNullsFirst, List *runCondition, + RPSkipTo rpSkipTo, List *patternVariable, List *patternRegexp, List *defineClause, + List *qual, bool topWindow, Plan *lefttree); static Group *make_group(List *tlist, List *qual, int numGroupCols, AttrNumber *grpColIdx, Oid *grpOperators, Oid *grpCollations, Plan *lefttree); @@ -2684,6 +2684,10 @@ create_windowagg_plan(PlannerInfo *root, WindowAggPath *best_path) wc->inRangeAsc, wc->inRangeNullsFirst, wc->runCondition, + wc->rpSkipTo, + wc->patternVariable, + wc->patternRegexp, + wc->defineClause, best_path->qual, best_path->topwindow, subplan); @@ -6580,8 +6584,9 @@ make_windowagg(List *tlist, Index winref, int ordNumCols, AttrNumber *ordColIdx, Oid *ordOperators, Oid *ordCollations, int frameOptions, Node *startOffset, Node *endOffset, Oid startInRangeFunc, Oid endInRangeFunc, - Oid inRangeColl, bool inRangeAsc, bool inRangeNullsFirst, - List *runCondition, List *qual, bool topWindow, Plan *lefttree) + Oid inRangeColl, bool inRangeAsc, bool inRangeNullsFirst, List *runCondition, + RPSkipTo rpSkipTo, List *patternVariable, List *patternRegexp, List *defineClause, + List *qual, bool topWindow, Plan *lefttree) { WindowAgg *node = makeNode(WindowAgg); Plan *plan = &node->plan; @@ -6607,6 +6612,10 @@ make_windowagg(List *tlist, Index winref, node->inRangeAsc = inRangeAsc; node->inRangeNullsFirst = inRangeNullsFirst; node->topWindow = topWindow; + node->rpSkipTo = rpSkipTo, + node->patternVariable = patternVariable; + node->patternRegexp = patternRegexp; + node->defineClause = defineClause; plan->targetlist = tlist; plan->lefttree = lefttree; diff --git a/src/include/nodes/plannodes.h b/src/include/nodes/plannodes.h index 1b787fe031..cc942b9c12 100644 --- a/src/include/nodes/plannodes.h +++ b/src/include/nodes/plannodes.h @@ -1096,6 +1096,18 @@ typedef struct WindowAgg /* nulls sort first for in_range tests? */ bool inRangeNullsFirst; + /* Row Pattern Recognition AFTER MACH SKIP clause */ + RPSkipTo rpSkipTo; /* Row Pattern Skip To type */ + + /* Row Pattern Recognition PATTERN variable name (list of String) */ + List *patternVariable; + + /* Row Pattern Recognition PATTERN regular expression quantifier ('+' or ''. list of String) */ + List *patternRegexp; + + /* Row Pattern Recognition DEFINE clause (list of TargetEntry) */ + List *defineClause; + /* * false for all apart from the WindowAgg that's closest to the root of * the plan -- 2.25.1 ----Next_Part(Mon_Jun_26_17_45_07_2023_724)-- Content-Type: Text/X-Patch; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="v2-0004-Row-pattern-recognition-patch-executor.patch" ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/[email protected] --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-07 14:44 Andres Freund <[email protected]> 0 siblings, 0 replies; 573+ messages in thread From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw) Some BF animals use very high timeouts due to their slowness. Unfortunately postmaster/003_start_stop fails if a high timeout is configured, due to authentication_timeout having a fairly low max. As this test is reasonably fast, the easiest fix seems to be to cap the timeout to 600. Per buildfarm animal skink. Reviewed-by: Heikki Linnakangas <[email protected]> Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --q4d36jgrlhdhudrc-- ^ permalink raw reply [nested|flat] 573+ messages in thread
end of thread, other threads:[~2025-03-07 14:44 UTC | newest] Thread overview: 573+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2023-06-26 08:05 [PATCH v2 3/7] Row pattern recognition patch (planner). Tatsuo Ishii <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]> 2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <[email protected]>
This inbox is served by agora; see mirroring instructions for how to clone and mirror all data and code used for this inbox