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

Commit4a1c0f3

Browse files
committed
Use a longer connection timeout in pg_isready test.
Buildfarm members skink and sungazer have both recently failed thistest, with symptoms indicating that the default 3-second timeoutisn't quite enough for those very slow systems. There's no reasonto be miserly with this timeout, so boost it to 60 seconds.Back-patch to all versions containing this test. That may be overkill,because the failure has only been observed in the v10 branch, butI don't feel like having to revisit this later.
1 parent655c938 commit4a1c0f3

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

‎src/bin/scripts/t/080_pg_isready.pl

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,4 +15,5 @@
1515
$node->init;
1616
$node->start;
1717

18-
$node->command_ok(['pg_isready'],'succeeds with server running');
18+
# use a long timeout for the benefit of very slow buildfarm machines
19+
$node->command_ok([qw(pg_isready --timeout=60)],'succeeds with server running');

0 commit comments

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