diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2020-08-04 15:20:31 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2020-08-04 15:20:31 -0400 |
| commit | f45cbed4c5781b30e7f4c4a500649b75f06bb0c3 (patch) | |
| tree | 1381fe5a37e7c6e4cc1356185219f2c2b51706e2 /src/interfaces/ecpg/test/expected/connect-test1.c | |
| parent | 995c53b44999c3a04ca54351dbc2d51bce82e55e (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-test1.c')
| -rw-r--r-- | src/interfaces/ecpg/test/expected/connect-test1.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/interfaces/ecpg/test/expected/connect-test1.c b/src/interfaces/ecpg/test/expected/connect-test1.c index 98b7e717c72..c4b22ac6c28 100644 --- a/src/interfaces/ecpg/test/expected/connect-test1.c +++ b/src/interfaces/ecpg/test/expected/connect-test1.c @@ -93,7 +93,7 @@ main(void) #line 47 "test1.pgc" - { ECPGconnect(__LINE__, 0, "unix:postgresql://localhost/ecpg2_regression?connect_timeout=14" , "regress_ecpg_user1" , NULL , NULL, 0); } + { ECPGconnect(__LINE__, 0, "unix:postgresql://localhost/ecpg2_regression?connect_timeout=180" , "regress_ecpg_user1" , NULL , NULL, 0); } #line 49 "test1.pgc" { ECPGdisconnect(__LINE__, "CURRENT");} |