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

From Nazir Bilal Yavuz
Subject Re: Heads Up: cirrus-ci is shutting down June 1st
Date
Msg-id CAN55FZ355yjig5RWOPzTj3-_c4iqdmAzjKLk6J_NuCnKjuG0GQ@mail.gmail.com
Whole thread Raw
In response to Re: Heads Up: cirrus-ci is shutting down June 1st  (Jelte Fennema-Nio <postgres@jeltef.nl>)
List pgsql-hackers
Hi,

On Fri, 10 Apr 2026 at 14:31, Jelte Fennema-Nio <postgres@jeltef.nl> wrote:
>
> On Thu, 9 Apr 2026 at 22:55, Andres Freund <andres@anarazel.de> wrote:
> > I'd be interested in feedback about how high folks value different aspects:
>
> My thoughts below.

I agree with all of Jelte's points except:

> > 4) CI tests as many operating systems as possible
>
> I think we at minimum need linux+macos+windows. Windows is by far the
> system that fails most often for me. BSDs would be good, but they
> often tend to be fine if osx and linux work. Personally for me I think
> on Cirrus The BSDs didn't meet the useful signal to flakiness noise
> ratio (i.e. they tended to mostly break randomly for me).

I think BSDs are quite capable of catching issues that others can't
catch. That has at least been my experience with OpenBSD.

However, I agree that OpenBSD and NetBSD tasks are flaky; I think that
is mostly because we generate these VM images from scratch (i.e. other
operating systems' VM images were already available on GCP). I don't
think FreeBSD is flaky.


-- 
Regards,
Nazir Bilal Yavuz
Microsoft



pgsql-hackers by date:

Previous
From: Jelte Fennema-Nio
Date:
Subject: Re: Heads Up: cirrus-ci is shutting down June 1st
Next
From: Dapeng Wang
Date:
Subject: Re: Add missing CHECK_FOR_INTERRUPTS in autovacuum catalog scan loops