Re: Heads Up: cirrus-ci is shutting down June 1st

From: Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com>
To: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Peter Eisentraut <peter(at)eisentraut(dot)org>, Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org, Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>
Subject: Re: Heads Up: cirrus-ci is shutting down June 1st
Date: 2026-06-17 11:21:32
Message-ID: CAN55FZ3ApNJ+SCosone0v5jHA3PzcGQUmOX7=T21-a43ayojuA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On Tue, 16 Jun 2026 at 02:20, Jacob Champion
<jacob(dot)champion(at)enterprisedb(dot)com> wrote:
>
> On Fri, Jun 12, 2026 at 2:54 PM Andres Freund <andres(at)anarazel(dot)de> wrote:
> > I did try creating an archive of an install, but that ends up with a good bit
> > of additional complexity, because the installations aren't relocatable (there
> > are header paths that are patched during install, apparently). And where the
> > install should be depends on the runner type, larger runners don't have D:,
> > but slower runners require using D:. I think Bilal hacked further on my
> > experiments around this, but I don't quite know where that stands. It's
> > certainly not a trivial change.
>
> Huh. (How does the current robocopy relocation work, then?)

The current robocopy step happens before the packages are installed.
Therefore, it seems there is nothing problematic with the default MSYS
installation, but rather that packages installed later cause the
problem.

--
Regards,
Nazir Bilal Yavuz
Microsoft

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Nisha Moond 2026-06-17 11:42:22 Re: [PATCH] Preserve replication origin OIDs in pg_upgrade
Previous Message Aleksander Alekseev 2026-06-17 11:07:04 Re: [PATCH] Fix segmentation fault and infinite loop in jsonb_{plperl,plpython}