Re: Ensure that STDERR is empty during connect_ok
От | Andrew Dunstan |
---|---|
Тема | Re: Ensure that STDERR is empty during connect_ok |
Дата | |
Msg-id | adc6e0b2-6b51-2510-44ad-8bfe8644eca6@dunslane.net обсуждение исходный текст |
Ответ на | Re: Ensure that STDERR is empty during connect_ok (Dagfinn Ilmari Mannsåker <ilmari@ilmari.org>) |
Ответы |
Re: Ensure that STDERR is empty during connect_ok
|
Список | pgsql-hackers |
On 2/2/22 11:01, Dagfinn Ilmari Mannsåker wrote: > Tom Lane <tgl@sss.pgh.pa.us> writes: > >> Daniel Gustafsson <daniel@yesql.se> writes: >> >>> While I prefer to not plan at all and instead run done_testing(), >>> doing that consistently is for another patch, keeping this with the >>> remainder of the suites. >> +1 to that too, counting the tests is a pretty useless exercise. > Rather than waiting for Someone™ to find a suitably-shaped tuit to do a > whole sweep converting everything to done_testing(), I think we should > make a habit of converting individual scripts whenever a change breaks > the count. Or when anyone edits a script, even if the number of tests doesn't get broken. cheers andrew -- Andrew Dunstan EDB: https://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: