Re: pgsql: Provide a TLS init hook
От | Tom Lane |
---|---|
Тема | Re: pgsql: Provide a TLS init hook |
Дата | |
Msg-id | 10659.1585230611@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: pgsql: Provide a TLS init hook (Andrew Dunstan <andrew.dunstan@2ndquadrant.com>) |
Ответы |
Re: pgsql: Provide a TLS init hook
|
Список | pgsql-committers |
Andrew Dunstan <andrew.dunstan@2ndquadrant.com> writes: > On 3/25/20 9:28 PM, Tom Lane wrote: >> jacana has just exposed a different problem: it's not configured >> --with-openssl, but the buildfarm script is trying to run this >> new test module anyway. I'm confused about the reason. >> "make installcheck" in src/test/modules does the right thing, >> but seemingly that client is doing something different? > Ugh. I have put in place a hack to clear the error on jacana. Yes, the > client does something different so we can run each module separately. > Trawling through the output and files for one test on its own is hard > enough, I don't want to aggregate them. Well, I'm confused, because my own critters are running this as part of a single make-installcheck-in-src/test/modules step, eg https://buildfarm.postgresql.org/cgi-bin/show_stage_log.pl?nm=longfin&dt=2020-03-26%2002%3A09%3A08&stg=testmodules-install-check-C Why is jacana doing it differently? regards, tom lane
В списке pgsql-committers по дате отправления: