Re: 'Bad file descriptor: dup2( 1, 2 )' error on MacOS CI tasks
| От | Tom Lane |
|---|---|
| Тема | Re: 'Bad file descriptor: dup2( 1, 2 )' error on MacOS CI tasks |
| Дата | |
| Msg-id | 2901836.1775053614@sss.pgh.pa.us обсуждение исходный текст |
| Ответ на | Re: 'Bad file descriptor: dup2( 1, 2 )' error on MacOS CI tasks (Andres Freund <andres@anarazel.de>) |
| Ответы |
Re: 'Bad file descriptor: dup2( 1, 2 )' error on MacOS CI tasks
|
| Список | pgsql-hackers |
Andres Freund <andres@anarazel.de> 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
В списке pgsql-hackers по дате отправления: