Re: Heads Up: cirrus-ci is shutting down June 1st - Mailing list pgsql-hackers

From Álvaro Herrera
Subject Re: Heads Up: cirrus-ci is shutting down June 1st
Date
Msg-id ahh972Lord8jglyO@alvherre.pgsql
Whole thread
In response to Re: Heads Up: cirrus-ci is shutting down June 1st  (Nazir Bilal Yavuz <byavuz81@gmail.com>)
Responses Re: Heads Up: cirrus-ci is shutting down June 1st
List pgsql-hackers
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.  20
minutes in, only the two "Linux - Meson" build finished, in 14 and 17
minutes respectively.  Macos took 10 minutes just for the macports
install!  Cirrus completed the same build in 18:32,
https://cirrus-ci.com/build/4817054382948352

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.  I hope we allow self-hosted runners
at some point; I have quite a bit of spare CPU capacity at home that I
could run the Linux and CompilerWarnings tasks on, leaving the Github
machines to run only the macOS and Windows ones.

-- 
Álvaro Herrera        Breisgau, Deutschland  —  https://www.EnterpriseDB.com/
"I'm impressed how quickly you are fixing this obscure issue. I came from 
MS SQL and it would be hard for me to put into words how much of a better job
you all are doing on [PostgreSQL]."
 Steve Midgley, http://archives.postgresql.org/pgsql-sql/2008-08/msg00000.php



pgsql-hackers by date:

Previous
From: Jacob Champion
Date:
Subject: Re: Make memory checking / sanitizing infrastructure better
Next
From: Robert Haas
Date:
Subject: Re: sandboxing untrusted code