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 CAN55FZ218TnSj90SMjY=fWqipM49iiqPYxVLMwwnGRWHy91WJA@mail.gmail.com
Whole thread
In response to Re: Heads Up: cirrus-ci is shutting down June 1st  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
Hi,

On Thu, 4 Jun 2026 at 22:03, Andres Freund <andres@anarazel.de> wrote:
>
> On 2026-06-04 09:02:13 -0700, Jacob Champion wrote:
> > On Thu, Jun 4, 2026 at 9:00 AM Andres Freund <andres@anarazel.de> wrote:
> > > > On the CPAN front, my first attempt tried to do too much, so I'm
> > > > testing a solution that just caches the CPAN sources directory. Should
> > > > have something shortly.
> > >
> > > I'm kinda inclined to push what we have and then add the cpan caching on top
> > > in subsequent commits?
> >
> > Right -- I don't think v1 should wait on CPAN optimization; I just
> > wanted to let you know the status.
>
> Pushed it now. Only a tiny change from the last version, Bilal suggested ove
> IM to remove the multi-threading argument from robocopy, for performance.

Thank you so much!

I realized one small problem today. When both Windows VS jobs fail, we
end up having two artifacts with the exactly same name. Here is a
small fix for it by adding '-slice-${slice_num}' to the end of the
artifact name.

--
Regards,
Nazir Bilal Yavuz
Microsoft

Attachment

pgsql-hackers by date:

Previous
From: Jacob Champion
Date:
Subject: Re: Prevent remote libpq notices from being sent to clients
Next
From: "Tristan Partin"
Date:
Subject: Re: dict_synonym.c: fix truncation of multibyte sequence