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 v3 2/3] remove lo_hton64() and lo_ntoh64() @ 2026-06-02 17:22 Reviewer <review@example.com> 0 siblings, 0 replies; 649+ messages in thread From: Reviewer @ 2026-06-02 17:22 UTC (permalink / raw) --- src/interfaces/libpq/fe-lobj.c | 58 +++------------------------------- 1 file changed, 4 insertions(+), 54 deletions(-) diff --git a/src/interfaces/libpq/fe-lobj.c b/src/interfaces/libpq/fe-lobj.c index 1660c969f58..42b2a36bda9 100644 --- a/src/interfaces/libpq/fe-lobj.c +++ b/src/interfaces/libpq/fe-lobj.c @@ -43,8 +43,6 @@ static int lo_initialize(PGconn *conn); static Oid lo_import_internal(PGconn *conn, const char *filename, Oid oid); -static int64_t lo_hton64(int64_t host64); -static int64_t lo_ntoh64(int64_t net64); /* * lo_open @@ -213,7 +211,7 @@ lo_truncate64(PGconn *conn, int fd, int64_t len) argv[0].len = 4; argv[0].u.integer = fd; - len = lo_hton64(len); + len = pg_hton64(len); argv[1].isint = 0; argv[1].len = 8; argv[1].u.ptr = (int *) &len; @@ -403,7 +401,7 @@ lo_lseek64(PGconn *conn, int fd, int64_t offset, int whence) argv[0].len = 4; argv[0].u.integer = fd; - offset = lo_hton64(offset); + offset = pg_hton64(offset); argv[1].isint = 0; argv[1].len = 8; argv[1].u.ptr = (int *) &offset; @@ -417,7 +415,7 @@ lo_lseek64(PGconn *conn, int fd, int64_t offset, int whence) if (PQresultStatus(res) == PGRES_COMMAND_OK && result_len == 8) { PQclear(res); - return lo_ntoh64(retval); + return pg_ntoh64(retval); } else { @@ -571,7 +569,7 @@ lo_tell64(PGconn *conn, int fd) if (PQresultStatus(res) == PGRES_COMMAND_OK && result_len == 8) { PQclear(res); - return lo_ntoh64(retval); + return pg_ntoh64(retval); } else { @@ -1014,51 +1012,3 @@ lo_initialize(PGconn *conn) conn->lobjfuncs = lobjfuncs; return 0; } - -/* - * lo_hton64 - * converts a 64-bit integer from host byte order to network byte order - */ -static int64_t -lo_hton64(int64_t host64) -{ - union - { - int64 i64; - uint32 i32[2]; - } swap; - uint32 t; - - /* High order half first, since we're doing MSB-first */ - t = (uint32) (host64 >> 32); - swap.i32[0] = pg_hton32(t); - - /* Now the low order half */ - t = (uint32) host64; - swap.i32[1] = pg_hton32(t); - - return swap.i64; -} - -/* - * lo_ntoh64 - * converts a 64-bit integer from network byte order to host byte order - */ -static int64_t -lo_ntoh64(int64_t net64) -{ - union - { - int64 i64; - uint32 i32[2]; - } swap; - int64 result; - - swap.i64 = net64; - - result = (uint32) pg_ntoh32(swap.i32[0]); - result <<= 32; - result |= (uint32) pg_ntoh32(swap.i32[1]); - - return result; -} -- 2.50.1 (Apple Git-155) --6CoALBM/+cswbGQ8 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=v3-0003-add-helper-functions-for-fast-path-arg-setup.patch ^ permalink raw reply [nested|flat] 649+ messages in thread
end of thread, other threads:[~2026-06-02 17:22 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-06-02 17:22 [PATCH v3 2/3] remove lo_hton64() and lo_ntoh64() Reviewer <review@example.com>
This inbox is served by agora; see mirroring instructions for how to clone and mirror all data and code used for this inbox