Re: CI, macports, darwin version problems

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: CI, macports, darwin version problems
Date: 2024-06-26 03:58:18
Message-ID: CA+hUKGJt6KzVTMhjHb3i+QwsRk7xfJKG1NRupUsg80mzAuYq4Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jun 26, 2024 at 12:00 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Thomas Munro <thomas(dot)munro(at)gmail(dot)com> writes:
> > I know how to find out which darwin version is running: uname -r | sed
> > 's/\..*//'. What I don't know is how to find the darwin version for a
> > macports installation.
>
> "port platform"?

Thanks, that's exactly what I was looking for.

But I thought of an easier way: instead of trying to do my own cache
invalidation with shell script and duct tape, I can include the
current OS major version in the cache key used to carry the
macports directory between CI runs. Hopefully Cirrus's cache machinery
is smart enough to age out the old stuff eventually.

This seems to have the desired effect. I've registered this thread to
see how cfbot likes this, and see if anyone sees a problem with
switching to the "macos-runner:sonoma" image, or the cache key scheme.

https://commitfest.postgresql.org/48/5076/

FTR there is a newer macOS release that recently came out, Sequoia aka
macOS 15, but the image available to us for CI is marked beta so I
figured we can wait a bit longer for that.

Attachment Content-Type Size
v2-0001-ci-Upgrade-macOS-version-from-13-to-14.patch application/x-patch 2.4 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2024-06-26 03:58:46 Re: speed up a logical replica setup
Previous Message Peter Smith 2024-06-26 03:45:40 Re: Improve the connection failure error messages