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

From: Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com>
To: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Cc: Andres Freund <andres(at)anarazel(dot)de>
Subject: macOS - Sequoia CI task is stuck on the Postgres Github CI
Date: 2025-11-26 13:44:00
Message-ID: CAN55FZ154XwzsOjkiDvbCvF_KMN3yjmkSTKpCCCaqTDEP0CXLQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

The PostgreSQL GitHub CI macOS tasks used to run on m4-dev, which I
believe was Andres’ worker machine. CC’ing Andres to check whether
something might be broken on the m4-dev worker.

[1] https://cirrus-ci.com/task/6157246901518336
[2] https://cirrus-ci.com/task/6393675590139904
[3] https://cirrus-ci.com/task/6039381187756032

--
Regards,
Nazir Bilal Yavuz
Microsoft

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Aleksander Alekseev 2025-11-26 13:49:49 Re: Question on PostgreSQL Table Partitioning – Performance of Queries That Do Not Use the Partition Key
Previous Message Aleksander Alekseev 2025-11-26 13:40:32 Re: [PATCH] psql: add size-based sorting options (O/o) for tables and indexes