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
Branch
------
REL_10_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/9bf2aeea8ea432b1a702313eae2186b4f946da21
Modified Files
--------------
src/interfaces/ecpg/test/connect/test1.pgc | 2 +-
src/interfaces/ecpg/test/connect/test5.pgc | 2 +-
src/interfaces/ecpg/test/expected/connect-test1-minGW32.stderr | 2 +-
src/interfaces/ecpg/test/expected/connect-test1.c | 2 +-
src/interfaces/ecpg/test/expected/connect-test1.stderr | 2 +-
src/interfaces/ecpg/test/expected/connect-test5.c | 2 +-
src/interfaces/ecpg/test/expected/connect-test5.stderr | 2 +-
7 files changed, 7 insertions(+), 7 deletions(-)