Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1w7wX9-0003Ql-0B for pgsql-hackers@arkaria.postgresql.org; Wed, 01 Apr 2026 14:27:03 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1w7wX7-000RlI-1M for pgsql-hackers@arkaria.postgresql.org; Wed, 01 Apr 2026 14:27:01 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1w7wX7-000Rl7-0T for pgsql-hackers@lists.postgresql.org; Wed, 01 Apr 2026 14:27:01 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1w7wX5-000000001RN-2zhG for pgsql-hackers@lists.postgresql.org; Wed, 01 Apr 2026 14:27:00 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 631EQshj2901837; Wed, 1 Apr 2026 10:26:54 -0400 From: Tom Lane To: Andres Freund cc: Nazir Bilal Yavuz , PostgreSQL Hackers , Noah Misch Subject: Re: 'Bad file descriptor: dup2( 1, 2 )' error on MacOS CI tasks In-reply-to: References: Comments: In-reply-to Andres Freund message dated "Wed, 01 Apr 2026 09:58:28 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2901835.1775053614.1@sss.pgh.pa.us> Date: Wed, 01 Apr 2026 10:26:54 -0400 Message-ID: <2901836.1775053614@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Andres Freund writes: > On 2026-04-01 16:28:21 +0300, Nazir Bilal Yavuz wrote: >> My current hypothesis is that all of these three tests use 'IO::Pty'. >> On MacOS CI, we install this via MacPorts using the 'p5.34-io-tty' >> package [2], which was updated about 2.5 days ago. I am not sure if is >> relevant but it has a known issue on Darwin [3]: > This presumably means that every macports user (e.g. Tom), will see this as > well after installing the latest updates. There must be some other factor involved. indri has been using p5.34-io-tty since I last did "port update" there, which looks to have been 22 March. And it's not failing. My laptop is also okay with these tests, and it likewise has $ port installed | grep io-.ty p5.34-io-tty @1.200.0_0 (active) indri and laptop are both on latest macOS Tahoe, maybe the problem only manifests on older releases? regards, tom lane