summaryrefslogtreecommitdiff
path: root/src/interfaces/ecpg/test/expected/connect-test5.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2020-08-04 15:20:31 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2020-08-04 15:20:31 -0400
commit0f76294260b92849c4958fb706ecd5b5cd73e40e (patch)
tree8ea9647ff8c5204a0e5d490e0a7c9617fa4d1574 /src/interfaces/ecpg/test/expected/connect-test5.c
parentdd877998d498c511352bd3640fd57f041c90ea62 (diff)
Increase hard-wired timeout values in ecpg regression tests.
A couple of test cases had connect_timeout=14, a value that seems to have been plucked from a hat. While it's more than sufficient for normal cases, slow/overloaded buildfarm machines can get a timeout failure here, as per recent report from "sungazer". Increase to 180 seconds, which is in line with our typical timeouts elsewhere in the regression tests. Back-patch to 9.6; the code looks different in 9.5, and this doesn't seem to be quite worth the effort to adapt to that. Report: https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=sungazer&dt=2020-08-04%2007%3A12%3A22
Diffstat (limited to 'src/interfaces/ecpg/test/expected/connect-test5.c')
-rw-r--r--src/interfaces/ecpg/test/expected/connect-test5.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/interfaces/ecpg/test/expected/connect-test5.c b/src/interfaces/ecpg/test/expected/connect-test5.c
index b44104854da..6ae5b589dea 100644
--- a/src/interfaces/ecpg/test/expected/connect-test5.c
+++ b/src/interfaces/ecpg/test/expected/connect-test5.c
@@ -121,7 +121,7 @@ main(void)
#line 56 "test5.pgc"
- { ECPGconnect(__LINE__, 0, "unix:postgresql://localhost/ecpg2_regression?connect_timeout=14 & client_encoding=latin1" , "regress_ecpg_user1" , "connectpw" , "main", 0); }
+ { ECPGconnect(__LINE__, 0, "unix:postgresql://localhost/ecpg2_regression?connect_timeout=180 & client_encoding=latin1" , "regress_ecpg_user1" , "connectpw" , "main", 0); }
#line 58 "test5.pgc"
{ ECPGdisconnect(__LINE__, "main");}