Updating IPC::Run in CI?

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

Hi all,

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.

Thanks,
--Jacob

[1] https://cirrus-ci.com/task/4537227113398272
[2] https://www.postgresql.org/message-id/fb666566-32bb-9c36-9c2e-3949b7a061bc%40gmail.com
[3] https://github.com/cpan-authors/IPC-Run/issues/176

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message John H 2025-09-18 17:20:22 Introduce XID age based replication slot invalidation
Previous Message Jonathan S. Katz 2025-09-18 16:59:13 Re: PG 18 relnotes and RC1