public inbox for [email protected]  

help / color / mirror / Atom feed

From: Dagfinn Ilmari Mannsåker <[email protected]>
To: Andrew Dunstan <[email protected]>
Cc: Ashutosh Bapat <[email protected]>
Cc: Peter Smith <[email protected]>
Cc: PostgreSQL Hackers <[email protected]>
Subject: Re: TAP test command_fails versus command_fails_like
Date: Wed, 12 Feb 2025 17:10:01 +0000
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <CAHut+Pu-umU=CkcSvrqL9eQt85Rv_qfLtekqU-yrjfh=GirUQg@mail.gmail.com>
	<CAExHW5vMkqvgxXOveB0_uRjYiCY319HK83Y-ErehcLyE0yv9Ww@mail.gmail.com>
	<[email protected]>
	<[email protected]>
	<[email protected]>

Dagfinn Ilmari Mannsåker <[email protected]> writes:

> Andrew Dunstan <[email protected]> writes:
>
>> On 2025-02-12 We 8:58 AM, Dagfinn Ilmari Mannsåker wrote:
>>>
>>>> Another question is whether command_fails and command_fails_like is
>>>> the only pair or there are more which need stricter checks?
>>> If we do this, we should do it across the board for
>>> PostgreSQL::Test::Utils and ::Cluster at least.  Once we bump the
>>> minimum perl version to 5.20 or beyond we should switch to using
>>> function signatures (https://perldoc.perl.org/perlsub#Signatures), which
>>> gives us this checking for free.
>>
>> Is there any reason we can't move to 5.20? Are there any buildfarm
>> animals using such an old version? 5.20 is now almost 10 years old.
>
> Red Hat Enterprise Linux 7 has Perl 5.16 and is on Extended Lifecycle
> Support until 2028-06-30. I don't know how long other distros based on
> that (e.g. CentOS, Scientific Linux) are supported, but I can see that
> Amazon Linux 2 is almost out of support (2025-06-30).

Ah, I found the thread from when we bumped it from 5.8 to 5.14 in 2022,
which has a list of then-current perl versions in the buildfarm:

https://postgr.es/m/20220902190329.jxvdeehkbfnrfmtl%40awork3.anarazel.de

- ilmari

view thread (3+ messages)

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: TAP test command_fails versus command_fails_like
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox