Re: how to manage Cirrus on personal repository - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: how to manage Cirrus on personal repository
Date
Msg-id CA+hUKG+NkOKTz3aoRijXvVCN=1=TZwQkWqmn6LCrDZtMx8snHQ@mail.gmail.com
Whole thread Raw
In response to Re: how to manage Cirrus on personal repository  (Nazir Bilal Yavuz <byavuz81@gmail.com>)
Responses Re: how to manage Cirrus on personal repository
List pgsql-hackers
On Sat, Sep 30, 2023 at 3:35 AM Nazir Bilal Yavuz <byavuz81@gmail.com> wrote:
> On Fri, 29 Sept 2023 at 13:24, Peter Eisentraut <peter@eisentraut.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



pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: Eager page freeze criteria clarification
Next
From: Tom Lane
Date:
Subject: Re: dikkop seems unhappy because of openssl stuff (FreeBSD 14-BETA1)