Feedback-ID: ie3de48e3:Fastmail
Date: Thu, 28 May 2026 20:42:41 +0200
From: =?utf-8?Q?=C3=81lvaro?= Herrera <alvherre@kurilemu.de>
To: Nazir Bilal Yavuz <byavuz81@gmail.com>
Cc: Andres Freund <andres@anarazel.de>,
	Jelte Fennema-Nio <postgres@jeltef.nl>,
 Thomas Munro <thomas.munro@gmail.com>,
	pgsql-hackers@postgresql.org, Zsolt Parragi <zsolt.parragi@percona.com>,
	Peter Eisentraut <peter@eisentraut.org>
Subject: Re: Heads Up: cirrus-ci is shutting down June 1st
Message-ID: <ahiLmvtaFWnTsFVu@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <ahh972Lord8jglyO@alvherre.pgsql>
Archived-At: 
 <https://www.postgresql.org/message-id/ahiLmvtaFWnTsFVu%40alvherre.pgsql>
Precedence: bulk

On 2026-May-28, Álvaro Herrera wrote:

> Hi, I just pushed this to github to see how it would behave.  In case
> anyone is curious, the run is here,
> 
> https://github.com/alvherre/postgres/actions/runs/26591496806
> 
> Overall I get the impression that it's much slower than Cirrus.  [...]
> 
> If I read the Github docs correctly, I get 2000 run minutes for free
> each month.  That would mean I can run at most some ... 15 runs per
> month?  That sounds quite limiting.

It ended up taking 3 hours 3 minutes, which means I can do 10.9 of those
per month.  Further runs will take less time due to ccache I suppose,
but the actual build is not a huge fraction of the total run time.
Linux+CompilerWarnings totalled 89 minutes; if I subtract those from the
total, I need 94 minutes to run the other builds, and then I can do 21.2
runs per month.

-- 
Álvaro Herrera        Breisgau, Deutschland  —  https://www.EnterpriseDB.com/