Re: Updating IPC::Run in CI?

From: Andres Freund <andres(at)anarazel(dot)de>
To: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Noah Misch <noah(at)leadboat(dot)com>
Subject: Re: Updating IPC::Run in CI?
Date: 2025-09-18 18:18:20
Message-ID: 5r4rda326g2j2las6bt7fpu6zmybopk4gnpwzcsssyrgs6spvp@dylpbqdj6ph5
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On 2025-09-18 10:08:49 -0700, Jacob Champion wrote:
> Andres pointed out that one of my new OAuth tests has flaked on NetBSD
> [1]. The final line of debugging output is missing from the stderr
> coming from psql.
>
> I haven't ruled out a bug in my implementation, but I also remembered
> that there was some discussion on the list about stderr being lost by
> IPC::Run in rare circumstances [2], and that particular bug has since
> been fixed [3]. Is it possible to (safely) switch the CI images to use
> the most recent IPC::Run, so we can make use of Noah's fixes? NetBSD
> is currently running 20231003.0.

A lot of things are safely possible :).

The stuff that's installed in the images is controlled by a bunch of scripts
in my pg-vm-images repository. For netbsd the relevant install is in

https://github.com/anarazel/pg-vm-images/blob/main/scripts/bsd/netbsd-prep-postgres.sh

As you can see we currently don't install packages from outside netbsd's
package repository. We could change that and install IPC::Run via cpan, but
imo it's obviously nicer - and more representative of real world setups - if
we just rely on OS/distro packages.

I don't know what would be required to get netbsd to upate their IPC::Run
package.
https://ftp.netbsd.org/pub/pkgsrc/current/pkgsrc/devel/p5-IPC-Run/index.html

If it were merged into netbsd, it'd be used for the CI images within a few
days, they are regenerated every few days [1] (or if a change the the image
sources is merged).

Greetings,

Andres Freund

[1] the cron-like expression is "0 30 0 ? * SUN,TUE,THU *", probably because I
didn't want to have to look at failures on Friday, Saturday

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Bossart 2025-09-18 18:19:30 Re: PG 18 relnotes and RC1
Previous Message Masahiko Sawada 2025-09-18 18:15:37 Re: Proposal: Conflict log history table for Logical Replication