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

From Julien Rouhaud
Subject Re: Replacing TAP test planning with done_testing()
Date
Msg-id CAOBaU_aw3K32HPzVTnQrjvx0cjG8H1LU1H69Z0U7oa1UqUDfow@mail.gmail.com
Whole thread Raw
In response to Re: Replacing TAP test planning with done_testing()  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
List pgsql-hackers
Le sam. 12 févr. 2022 à 04:28, Alvaro Herrera <alvherre@alvh.no-ip.org> a écrit :
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

+1

pgsql-hackers by date:

Previous
From: Anders Kaseorg
Date:
Subject: Re: PGroonga index-only scan problem with yesterday’s PostgreSQL updates
Next
From: Andres Freund
Date:
Subject: Re: Race condition in TransactionIdIsInProgress