NotificationsYou must be signed in to change notification settings
Fork28
Star151

Commit1a6b2b1

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 parente775dd6 commit1a6b2b1Copy full SHA for 1a6b2b1

File tree

1 file changed

-1

lines changed

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

1 file changed

-1

lines changed

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

Lines changed: 2 additions & 1 deletion

Original file line number	Diff line number	Diff line change
`@@ -15,4 +15,5 @@`
`15`	`15`	`$node->init;`
`16`	`16`	`$node->start;`
`17`	`17`
`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)

Movatterモバイル変換

Navigation Menu

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

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Commit1a6b2b1

File tree

1 file changed

1 file changed

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

0 commit comments