Re: Mop-up from Test::More version change patch

2021-11-23 Thread Peter Eisentraut
On 23.11.21 18:03, Tom Lane wrote: 0002 is written to apply to v14 and earlier, and what it wants to do is back-patch the effects of 405f32fc4, so that the minimum Test::More version is 0.98 in all branches. The thought here is that (1) somebody is likely to want to back-patch a test involving T

Re: Mop-up from Test::More version change patch

2021-11-23 Thread Noah Misch
On Tue, Nov 23, 2021 at 12:03:05PM -0500, Tom Lane wrote: > Attached are a couple of patches I propose in the wake of commit > 405f32fc4 (Require version 0.98 of Test::More for TAP tests). > > 0001 responds to the failure we saw on buildfarm member wrasse [1] > where, despite configure having care

Re: Mop-up from Test::More version change patch

2021-11-23 Thread Tom Lane
Andrew Dunstan writes: > On 11/23/21 12:03, Tom Lane wrote: >> If you set PERL then it's highly likely that you want to use >> "prove" from the same installation. So 0001 modifies configure >> to first check for an executable "prove" in the same directory >> as $PERL. If that's not what you want

Re: Mop-up from Test::More version change patch

2021-11-23 Thread Andrew Dunstan
On 11/23/21 12:03, Tom Lane wrote: > [ moving thread to -hackers for a bit more visibility ] > > Attached are a couple of patches I propose in the wake of commit > 405f32fc4 (Require version 0.98 of Test::More for TAP tests). > > 0001 responds to the failure we saw on buildfarm member wrasse [1]

Mop-up from Test::More version change patch

2021-11-23 Thread Tom Lane
[ moving thread to -hackers for a bit more visibility ] Attached are a couple of patches I propose in the wake of commit 405f32fc4 (Require version 0.98 of Test::More for TAP tests). 0001 responds to the failure we saw on buildfarm member wrasse [1] where, despite configure having carefully check