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

From Alvaro Herrera
Subject Re: Replacing TAP test planning with done_testing()
Date
Msg-id 202202112028.we5v7c6f5hay@alvherre.pgsql
Whole thread Raw
In response to Re: Replacing TAP test planning with done_testing()  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Replacing TAP test planning with done_testing()  (Julien Rouhaud <rjuju123@gmail.com>)
List pgsql-hackers
On 2022-Feb-11, Tom Lane wrote:

> Andres Freund <andres@anarazel.de> writes:

> > +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.

+1

-- 
Álvaro Herrera         PostgreSQL Developer  —  https://www.EnterpriseDB.com/



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: support for MERGE
Next
From: Andrew Dunstan
Date:
Subject: Re: [Proposal] Fully WAL logged CREATE DATABASE - No Checkpoints