Increase hard-wired timeout values in ecpg regression tests.
authorTom Lane <tgl@sss.pgh.pa.us>
Tue, 4 Aug 2020 19:20:31 +0000 (15:20 -0400)
committerTom Lane <tgl@sss.pgh.pa.us>
Tue, 4 Aug 2020 19:20:31 +0000 (15:20 -0400)
commit0f76294260b92849c4958fb706ecd5b5cd73e40e
tree8ea9647ff8c5204a0e5d490e0a7c9617fa4d1574
parentdd877998d498c511352bd3640fd57f041c90ea62
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
src/interfaces/ecpg/test/connect/test1.pgc
src/interfaces/ecpg/test/connect/test5.pgc
src/interfaces/ecpg/test/expected/connect-test1-minGW32.stderr
src/interfaces/ecpg/test/expected/connect-test1.c
src/interfaces/ecpg/test/expected/connect-test1.stderr
src/interfaces/ecpg/test/expected/connect-test5.c
src/interfaces/ecpg/test/expected/connect-test5.stderr