Re: Replacing TAP test planning with done_testing() - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Replacing TAP test planning with done_testing()
Date
Msg-id 20220211201622.zuv43oh2zg76sdc2@alap3.anarazel.de
Whole thread Raw
In response to Re: Replacing TAP test planning with done_testing()  (Daniel Gustafsson <daniel@yesql.se>)
Responses Re: Replacing TAP test planning with done_testing()  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
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.



pgsql-hackers by date:

Previous
From: Daniel Gustafsson
Date:
Subject: Re: Replacing TAP test planning with done_testing()
Next
From: Tom Lane
Date:
Subject: Re: Replacing TAP test planning with done_testing()