agora inbox for pgsql-hackers@postgresql.orghelp / color / mirror / Atom feed
[PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop 649+ messages / 2 participants [nested] [flat]
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low connection limits, to test dead-end backends -- 2.48.1.76.g4e746b1a31.dirty --ds7cemehex757p34-- ^ permalink raw reply [nested|flat] 649+ messages in thread
* [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop @ 2025-03-06 20:13 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 649+ messages in thread From: Andres Freund @ 2025-03-06 20:13 UTC (permalink / raw) Per buildfarm animal skink. Discussion: https://postgr.es/m/20250306044933.7a.nmisch@google.com --- src/test/postmaster/t/003_start_stop.pl | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/test/postmaster/t/003_start_stop.pl b/src/test/postmaster/t/003_start_stop.pl index 036b296f72b..4dc394139d9 100644 --- a/src/test/postmaster/t/003_start_stop.pl +++ b/src/test/postmaster/t/003_start_stop.pl @@ -20,6 +20,10 @@ use Test::More; # "pg_ctl stop" will error out before the authentication timeout kicks # in and cleans up the dead-end backends. my $authentication_timeout = $PostgreSQL::Test::Utils::timeout_default; + +# Don't fail due to hitting the max value allowed for authentication_timeout. +$authentication_timeout = 600 unless $authentication_timeout < 600; + my $stop_timeout = $authentication_timeout / 2; # Initialize the server with low 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
* [PATCH v1 2/2] run pgindent @ 2026-05-05 21:04 Nathan Bossart <nathan@postgresql.org> 0 siblings, 0 replies; 649+ messages in thread From: Nathan Bossart @ 2026-05-05 21:04 UTC (permalink / raw) --- src/backend/replication/logical/logicalfuncs.c | 2 +- src/backend/storage/ipc/dsm_registry.c | 2 +- src/bin/pg_basebackup/pg_basebackup.c | 6 +++--- 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/src/backend/replication/logical/logicalfuncs.c b/src/backend/replication/logical/logicalfuncs.c index 512013b0ef0..71fbaf72269 100644 --- a/src/backend/replication/logical/logicalfuncs.c +++ b/src/backend/replication/logical/logicalfuncs.c @@ -218,7 +218,7 @@ pg_logical_slot_get_changes_guts(FunctionCallInfo fcinfo, bool confirm, bool bin * what we need. */ if (!binary && - ctx->options.output_type !=OUTPUT_PLUGIN_TEXTUAL_OUTPUT) + ctx->options.output_type != OUTPUT_PLUGIN_TEXTUAL_OUTPUT) ereport(ERROR, (errcode(ERRCODE_FEATURE_NOT_SUPPORTED), errmsg("logical decoding output plugin \"%s\" produces binary output, but function \"%s\" expects textual data", diff --git a/src/backend/storage/ipc/dsm_registry.c b/src/backend/storage/ipc/dsm_registry.c index 2b56977659b..b9961c26019 100644 --- a/src/backend/storage/ipc/dsm_registry.c +++ b/src/backend/storage/ipc/dsm_registry.c @@ -479,7 +479,7 @@ pg_get_dsm_registry_allocations(PG_FUNCTION_ARGS) entry->dsa.handle != DSA_HANDLE_INVALID) vals[2] = Int64GetDatum(dsa_get_total_size_from_handle(entry->dsa.handle)); else if (entry->type == DSMR_ENTRY_TYPE_DSH && - entry->dsh.dsa_handle !=DSA_HANDLE_INVALID) + entry->dsh.dsa_handle != DSA_HANDLE_INVALID) vals[2] = Int64GetDatum(dsa_get_total_size_from_handle(entry->dsh.dsa_handle)); else nulls[2] = true; diff --git a/src/bin/pg_basebackup/pg_basebackup.c b/src/bin/pg_basebackup/pg_basebackup.c index c1a4672aa6f..80dc3bbc8da 100644 --- a/src/bin/pg_basebackup/pg_basebackup.c +++ b/src/bin/pg_basebackup/pg_basebackup.c @@ -1282,7 +1282,7 @@ ReceiveArchiveStream(PGconn *conn, pg_compress_specification *compress) ReceiveCopyData(conn, ReceiveArchiveStreamChunk, &state); /* If we wrote the backup manifest to a file, close the file. */ - if (state.manifest_file !=NULL) + if (state.manifest_file != NULL) { fclose(state.manifest_file); state.manifest_file = NULL; @@ -1341,7 +1341,7 @@ ReceiveArchiveStreamChunk(size_t r, char *copybuf, void *callback_data) /* Sanity check. */ if (state->manifest_buffer != NULL || - state->manifest_file !=NULL) + state->manifest_file != NULL) pg_fatal("archives must precede manifest"); /* Parse the rest of the CopyData message. */ @@ -1406,7 +1406,7 @@ ReceiveArchiveStreamChunk(size_t r, char *copybuf, void *callback_data) appendPQExpBuffer(state->manifest_buffer, copybuf + 1, r - 1); } - else if (state->manifest_file !=NULL) + else if (state->manifest_file != NULL) { /* Manifest data, write to disk. */ if (fwrite(copybuf + 1, r - 1, 1, -- 2.50.1 (Apple Git-155) --k2Vi/uo5iFea1Gni-- ^ permalink raw reply [nested|flat] 649+ messages in thread
end of thread, other threads:[~2026-05-05 21:04 UTC | newest] Thread overview: 649+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH v1 4/4] tests: Don't fail due to high default timeout in postmaster/003_start_stop Andres Freund <andres@anarazel.de> 2025-03-06 20:13 [PATCH 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> 2026-05-05 21:04 [PATCH v1 2/2] run pgindent Nathan Bossart <nathan@postgresql.org>
This inbox is served by agora; see mirroring instructions for how to clone and mirror all data and code used for this inbox