Re: how to manage Cirrus on personal repository

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com>
Cc: Peter Eisentraut <peter(at)eisentraut(dot)org>, Daniel Gustafsson <daniel(at)yesql(dot)se>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: how to manage Cirrus on personal repository
Date: 2023-09-29 22:02:15
Message-ID: CA+hUKG+NkOKTz3aoRijXvVCN=1=TZwQkWqmn6LCrDZtMx8snHQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Sep 30, 2023 at 3:35 AM Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com> wrote:
> On Fri, 29 Sept 2023 at 13:24, Peter Eisentraut <peter(at)eisentraut(dot)org> wrote:
> > I have a private repository on GitHub where I park PostgreSQL
> > development work. I also have Cirrus activated on that repository, to
> > build those branches, using the existing Cirrus configuration.
> >
> > Now under the new system of limited credits that started in September,
> > this blew through the credits about half-way through the month.

[Replying to wrong person because I never saw Peter's original email,
something must be jammed in the intertubes...]

It's annoying, but on the bright side... if you're making it halfway
through the month, I think that means there's a chance you'd have
enough credit if we can depessimise the known problems with TAP query
execution[1], and there are some more obviously stupid things too
(sleep/poll for replication progress where PostgreSQL should offer an
event-based wait-for-replay, running all the tests when only docs
changed, running the regression tests fewer times, ...).

[1] https://www.postgresql.org/message-id/flat/CA%2BhUKGJoEO33K%3DZynsH%3DxkiEyfBMZjOoqBK%2BgouBdTGW2-woig%40mail.gmail.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2023-09-29 22:05:07 Re: dikkop seems unhappy because of openssl stuff (FreeBSD 14-BETA1)
Previous Message Peter Geoghegan 2023-09-29 21:58:36 Re: Eager page freeze criteria clarification