Re: macOS - Sequoia CI task is stuck on the Postgres Github CI

From: Álvaro Herrera <alvherre(at)kurilemu(dot)de>
To: Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de>
Subject: Re: macOS - Sequoia CI task is stuck on the Postgres Github CI
Date: 2025-11-26 14:38:37
Message-ID: 202511261426.6rgu7f2z35pc@alvherre.pgsql
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2025-Nov-26, Nazir Bilal Yavuz wrote:

> Hi,
>
> I noticed that the macOS – Sequoia CI task is stuck on the PostgreSQL
> GitHub CI [1], while the same task runs successfully on the CFBot [2].
> On the CFBot, the worker jc-m2-1 is used, but the PostgreSQL GitHub CI
> does not show a specific worker name although it reports
> instance:PersistentWorkerInstance.

Maybe the problem is just that the macOS workers are too busy? If I go
to https://cirrus-ci.com/github/postgres/postgres/master I see a bunch
that are marked as "executing", and if you open those, you see that
they're all waiting until the "MacOS - Sequoia" task to complete, which
is state Scheduled. ... and while I was looking at one, it switched to
running.

(I only came here to report that buildfarm member Prion gets stuck in
one of the new test cases added by bc32a12e0db2. The culprit is
CATCACHE_FORCE_RELEASE. Not relevant to your investigation.)

--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
<Schwern> It does it in a really, really complicated way
<crab> why does it need to be complicated?
<Schwern> Because it's MakeMaker.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2025-11-26 14:44:51 Re: macOS - Sequoia CI task is stuck on the Postgres Github CI
Previous Message Daniel Gustafsson 2025-11-26 14:33:07 Re: Serverside SNI support in libpq