Re: Replacing TAP test planning with done_testing()
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
Cc: Daniel Gustafsson <daniel@yesql.se>, Michael Paquier <michael@paquier.xyz>, Dagfinn Ilmari Mannsåker <ilmari@ilmari.org>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2022-02-11T20:22:41Z
Lists: pgsql-hackers
Andres Freund <andres@anarazel.de> writes: > On 2022-02-11 21:04:53 +0100, Daniel Gustafsson wrote: >> I opted out of backpatching for now, to solicit more comments on that. It's >> not a bugfix, but it's also not affecting the compiled bits that we ship, so I >> think there's a case to be made both for and against a backpatch. Looking at >> the oldest branch we support, it seems we've done roughly 25 changes to the >> test plans in REL_10_STABLE over the years, so it's neither insignificant nor >> an everyday activity. Personally I don't have strong opinions, what do others >> think? > +1 on backpatching. Backpatching tests now is less likely to cause conflicts, > but more likely to fail during tests. If you've got the energy to do it, +1 for backpatching. I agree with Michael's opinion that doing so will probably save us future annoyance. regards, tom lane
Commits
-
Replace Test::More plans with done_testing
- 549ec201d613 15.0 landed