Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commitb48832c

Browse files
committed
tests: Don't fail due to high default timeout in postmaster/003_start_stop
Some BF animals use very high timeouts due to their slowness. Unfortunatelypostmaster/003_start_stop fails if a high timeout is configured, due toauthentication_timeout having a fairly low max.As this test is reasonably fast, the easiest fix seems to be to cap thetimeout to 600.Per buildfarm animal skink.Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>Discussion:https://postgr.es/m/ggflhkciwdyotpoie323chu2c2idpjk5qimrn462encwx2io7s@thmcxl7i6dpw
1 parent71d1ed6 commitb48832c

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

‎src/test/postmaster/t/003_start_stop.pl

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -20,6 +20,10 @@
2020
# "pg_ctl stop" will error out before the authentication timeout kicks
2121
# in and cleans up the dead-end backends.
2222
my$authentication_timeout =$PostgreSQL::Test::Utils::timeout_default;
23+
24+
# Don't fail due to hitting the max value allowed for authentication_timeout.
25+
$authentication_timeout = 600unless$authentication_timeout < 600;
26+
2327
my$stop_timeout =$authentication_timeout / 2;
2428

2529
# Initialize the server with low connection limits, to test dead-end backends

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp