18.10.2020 21:04, Tom Lane wrote: > Alexander Lakhin <exclus...@gmail.com> writes: >> @@ -0,0 +1 @@ >> +SQL error: descriptor "mydesc" not found on line 31 > does not look like the same kind of failure as what we've been dealing > with up to now. So maybe what we've got is that we fixed the stdio > loss problem, and now the error rate is down to the point where we can > notice other, even-lower-probability issues. Yes, in this case stderr is not missing (it's present with the error). So it's really different case. As is another one:
test connect/test5 ... stderr FAILED 238 ms diff -w -U3 .../src/interfaces/ecpg/test/expected/connect-test5.stderr .../src/interfaces/ecpg/test/results/connect-test5.stderr --- .../src/interfaces/ecpg/test/expected/connect-test5.stderr 2020-10-13 21:51:14 +0300 +++ .../src/interfaces/ecpg/test/results/connect-test5.stderr 2020-10-18 20:59:46 +0300 @@ -73,7 +73,9 @@ [NO_PID]: sqlca: code: -220, state: 08003 [NO_PID]: ECPGconnect: opening database <DEFAULT> on <DEFAULT> port <DEFAULT> for user regress_ecpg_user2 [NO_PID]: sqlca: code: 0, state: 00000 -[NO_PID]: ECPGconnect: could not open database: FATAL: database "regress_ecpg_user2" does not exist +[NO_PID]: ECPGconnect: could not open database: server closed the connection unexpectedly + This probably means the server terminated abnormally + before or while processing the request. and the server.log: 2020-10-18 20:59:45.731 MSK client backend[1380] ecpg/connect-test4 LOG: could not receive data from client: An existing connection was forcibly closed by the remote host. 2020-10-18 20:59:45.898 MSK client backend[2884] [unknown] FATAL: database "regress_ecpg_user2" does not exist 2020-10-18 20:59:45.992 MSK client backend[1640] [unknown] FATAL: database "regress_ecpg_user2" does not exist I just wanted to inform that the ECPG-test failures can still persist in the buildfarm, unfortunately. Best regards, Alexander