Re: Updating IPC::Run in CI?

Hi,

On Thu, 18 Sept 2025 at 21:18, Andres Freund <andres(at)anarazel(dot)de> wrote:
>
> 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 have not checked it yet but we are on NetBSD 10.0 [1]. I thought
upgrading to 10.1 might help... Apparently it does not, 10.1 too uses
p5-IPC-Run-20231003 [2].

[1] https://github.com/anarazel/pg-vm-images/blob/main/packer/netbsd.pkrvars.hcl#L58C1-L58C75
[2] https://ftp.netbsd.org/pub/pkgsrc/current/pkgsrc/index-all.html

--
Regards,
Nazir Bilal Yavuz
Microsoft