| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Dagfinn Ilmari Mannsåker <ilmari(at)ilmari(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Replacing TAP test planning with done_testing() |
| Date: | 2022-02-11 20:16:22 |
| Message-ID: | 20220211201622.zuv43oh2zg76sdc2@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2022-02-11 20:22:41 | Re: Replacing TAP test planning with done_testing() |
| Previous Message | Daniel Gustafsson | 2022-02-11 20:04:53 | Re: Replacing TAP test planning with done_testing() |