| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Daniel Gustafsson <daniel(at)yesql(dot)se>, Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Melanie Plageman <melanieplageman(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, mikael(dot)kjellstrom(at)gmail(dot)com |
| Subject: | Re: Making background psql nicer to use in tap tests |
| Date: | 2023-04-08 00:38:03 |
| Message-ID: | 3266862.1680914283@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>> Actually, one quick datapoint. prion and mantid report running IPC::Run
>> version 0.92, and morepork 0.96. Animals that pass are running 20180523.0,
>> 20200505.0, 20220807.0 or similar versions. We don't print the IO::Pty version
>> during configure, but maybe this is related to older versions of the modules
>> and this test (not all of them apparently) need to SKIP if IO::Pty is missing
>> or too old? Somewhere to start looking at the very least.
> prion was running 1.10 (dated to 2010). I have just updated it to 1.17
> (the CPAN latest). We'll see if that makes a difference.
I've been doing some checking with perlbrew locally. It appears to not
be about IO::Pty so much as IPC::Run: it works with IPC::Run 0.99 but
not 0.79. Still bisecting to identify exactly what's the minimum
okay version.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2023-04-08 00:41:47 | Re: cataloguing NOT NULL constraints |
| Previous Message | Andres Freund | 2023-04-08 00:19:42 | Re: cataloguing NOT NULL constraints |