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.
