agora inbox for pgsql-hackers@postgresql.org
help / color / mirror / Atom feed[PATCH v34 01/11] Add a syntax to create Incrementally Maintainable Materialized Views
649+ messages / 2 participants
[nested] [flat]
* [PATCH v34 01/11] Add a syntax to create Incrementally Maintainable Materialized Views
@ 2019-12-20 01:05 Yugo Nagata <nagata@sraoss.co.jp>
0 siblings, 0 replies; 649+ messages in thread
From: Yugo Nagata @ 2019-12-20 01:05 UTC (permalink / raw)
Allow to create Incrementally Maintainable Materialized View (IMMV)
by using INCREMENTAL option in CREATE MATERIALIZED VIEW command
as follow:
CREATE [INCREMANTAL] MATERIALIZED VIEW xxxxx AS SELECT ....;
---
src/backend/parser/gram.y | 32 +++++++++++++++++++++-----------
src/include/nodes/primnodes.h | 1 +
src/include/parser/kwlist.h | 1 +
3 files changed, 23 insertions(+), 11 deletions(-)
diff --git a/src/backend/parser/gram.y b/src/backend/parser/gram.y
index a043fd4c66..943460fd2c 100644
--- a/src/backend/parser/gram.y
+++ b/src/backend/parser/gram.y
@@ -468,6 +468,7 @@ static Node *makeRecursiveViewSelect(char *relname, List *aliases, Node *query);
%type <range> OptTempTableName
%type <into> into_clause create_as_target create_mv_target
+%type <boolean> incremental
%type <defelt> createfunc_opt_item common_func_opt_item dostmt_opt_item
%type <fun_param> func_arg func_arg_with_default table_func_column aggr_arg
@@ -738,7 +739,7 @@ static Node *makeRecursiveViewSelect(char *relname, List *aliases, Node *query);
HANDLER HAVING HEADER_P HOLD HOUR_P
IDENTITY_P IF_P ILIKE IMMEDIATE IMMUTABLE IMPLICIT_P IMPORT_P IN_P INCLUDE
- INCLUDING INCREMENT INDENT INDEX INDEXES INHERIT INHERITS INITIALLY INLINE_P
+ INCLUDING INCREMENT INCREMENTAL INDENT INDEX INDEXES INHERIT INHERITS INITIALLY INLINE_P
INNER_P INOUT INPUT_P INSENSITIVE INSERT INSTEAD INT_P INTEGER
INTERSECT INTERVAL INTO INVOKER IS ISNULL ISOLATION
@@ -4803,32 +4804,34 @@ opt_with_data:
*****************************************************************************/
CreateMatViewStmt:
- CREATE OptNoLog MATERIALIZED VIEW create_mv_target AS SelectStmt opt_with_data
+ CREATE OptNoLog incremental MATERIALIZED VIEW create_mv_target AS SelectStmt opt_with_data
{
CreateTableAsStmt *ctas = makeNode(CreateTableAsStmt);
- ctas->query = $7;
- ctas->into = $5;
+ ctas->query = $8;
+ ctas->into = $6;
ctas->objtype = OBJECT_MATVIEW;
ctas->is_select_into = false;
ctas->if_not_exists = false;
/* cram additional flags into the IntoClause */
- $5->rel->relpersistence = $2;
- $5->skipData = !($8);
+ $6->rel->relpersistence = $2;
+ $6->skipData = !($9);
+ $6->ivm = $3;
$$ = (Node *) ctas;
}
- | CREATE OptNoLog MATERIALIZED VIEW IF_P NOT EXISTS create_mv_target AS SelectStmt opt_with_data
+ | CREATE OptNoLog incremental MATERIALIZED VIEW IF_P NOT EXISTS create_mv_target AS SelectStmt opt_with_data
{
CreateTableAsStmt *ctas = makeNode(CreateTableAsStmt);
- ctas->query = $10;
- ctas->into = $8;
+ ctas->query = $11;
+ ctas->into = $9;
ctas->objtype = OBJECT_MATVIEW;
ctas->is_select_into = false;
ctas->if_not_exists = true;
/* cram additional flags into the IntoClause */
- $8->rel->relpersistence = $2;
- $8->skipData = !($11);
+ $9->rel->relpersistence = $2;
+ $9->skipData = !($12);
+ $9->ivm = $3;
$$ = (Node *) ctas;
}
;
@@ -4845,9 +4848,14 @@ create_mv_target:
$$->tableSpaceName = $5;
$$->viewQuery = NULL; /* filled at analysis time */
$$->skipData = false; /* might get changed later */
+ $$->ivm = false;
}
;
+incremental: INCREMENTAL { $$ = true; }
+ | /*EMPTY*/ { $$ = false; }
+ ;
+
OptNoLog: UNLOGGED { $$ = RELPERSISTENCE_UNLOGGED; }
| /*EMPTY*/ { $$ = RELPERSISTENCE_PERMANENT; }
;
@@ -17686,6 +17694,7 @@ unreserved_keyword:
| INCLUDE
| INCLUDING
| INCREMENT
+ | INCREMENTAL
| INDENT
| INDEX
| INDEXES
@@ -18274,6 +18283,7 @@ bare_label_keyword:
| INCLUDE
| INCLUDING
| INCREMENT
+ | INCREMENTAL
| INDENT
| INDEX
| INDEXES
diff --git a/src/include/nodes/primnodes.h b/src/include/nodes/primnodes.h
index ea47652adb..6f01300a30 100644
--- a/src/include/nodes/primnodes.h
+++ b/src/include/nodes/primnodes.h
@@ -168,6 +168,7 @@ typedef struct IntoClause
/* materialized view's SELECT query */
Node *viewQuery pg_node_attr(query_jumble_ignore);
bool skipData; /* true for WITH NO DATA */
+ bool ivm; /* true for WITH IVM */
} IntoClause;
diff --git a/src/include/parser/kwlist.h b/src/include/parser/kwlist.h
index f7fe834cf4..1625fea602 100644
--- a/src/include/parser/kwlist.h
+++ b/src/include/parser/kwlist.h
@@ -210,6 +210,7 @@ PG_KEYWORD("in", IN_P, RESERVED_KEYWORD, BARE_LABEL)
PG_KEYWORD("include", INCLUDE, UNRESERVED_KEYWORD, BARE_LABEL)
PG_KEYWORD("including", INCLUDING, UNRESERVED_KEYWORD, BARE_LABEL)
PG_KEYWORD("increment", INCREMENT, UNRESERVED_KEYWORD, BARE_LABEL)
+PG_KEYWORD("incremental", INCREMENTAL, UNRESERVED_KEYWORD, BARE_LABEL)
PG_KEYWORD("indent", INDENT, UNRESERVED_KEYWORD, BARE_LABEL)
PG_KEYWORD("index", INDEX, UNRESERVED_KEYWORD, BARE_LABEL)
PG_KEYWORD("indexes", INDEXES, UNRESERVED_KEYWORD, BARE_LABEL)
--
2.34.1
--Multipart=_Thu__11_Jul_2024_13_23_57_+0900_hKsU2G3a3BgS2FFs
Content-Type: text/x-diff;
name="v34-0011-Add-documentations-about-Incremental-View-Mainte.patch"
Content-Disposition: attachment;
filename="v34-0011-Add-documentations-about-Incremental-View-Mainte.patch"
Content-Transfer-Encoding: 7bit
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-06 20:13 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw)
Per buildfarm animal skink.
Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--ds7cemehex757p34--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop
@ 2025-03-07 14:44 Andres Freund <andres@anarazel.de>
0 siblings, 0 replies; 649+ messages in thread
From: Andres Freund @ 2025-03-07 14:44 UTC (permalink / raw)
Some BF animals use very high timeouts due to their slowness. Unfortunately
postmaster/003_start_stop fails if a high timeout is configured, due to
authentication_timeout having a fairly low max.
As this test is reasonably fast, the easiest fix seems to be to cap the
timeout to 600.
Per buildfarm animal skink.
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
---
src/test/postmaster/t/003_start_stop.pl | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl
index 036b296f72b..4dc394139d9 100644
--- a/src/test/postmaster/t/003_start_stop.pl
+++ b/src/test/postmaster/t/003_start_stop.pl
@@ -20,6 +20,10 @@ use Test::More;
# "pg_ctl stop" will error out before the authentication timeout kicks
# in and cleans up the dead-end backends.
my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default;
+
+# Don't fail due to hitting the max value allowed for authentication_timeout.
+$authentication_timeout = 600 unless $authentication_timeout < 600;
+
my $stop_timeout = $authentication_timeout / 2;
# Initialize the server with low connection limits, to test dead-end backends
--
2.48.1.76.g4e746b1a31.dirty
--q4d36jgrlhdhudrc--
^ permalink raw reply [nested|flat] 649+ messages in thread
end of thread, other threads:[~2025-03-07 14:44 UTC | newest]
Thread overview: 649+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2019-12-20 01:05 [PATCH v34 01/11] Add a syntax to create Incrementally Maintainable Materialized Views Yugo Nagata <nagata@sraoss.co.jp>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
2025-03-07 14:44 [PATCH v2 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox