From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
---|---|
To: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Cirrus CI for macOS branches 16 and 15 broken |
Date: | 2024-08-18 22:01:55 |
Message-ID: | CA+hUKGL0A3PBnsrKo-p+awB=QMBuwRfucb1jo3GCYVXmBSi3GQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Aug 19, 2024 at 7:52 AM Thomas Munro <thomas(dot)munro(at)gmail(dot)com> wrote:
> The macOS major version and hash of the MacPorts package install
> script are in the cache key for that (see 64c39bd5), so a change to
> that script would make a totally fresh installation, and hopefully
> work. I will look into that, but it would also be nice to understand
> how it go itself into that state so we can avoid it...
Oh, it already is a cache miss and thus a fresh installation, in
Tomas's example. I can reproduce that in my own Github account by
making a trivial change to ci_macports_packages.sh to I get a cache
miss too. It appears to install macports just fine, and then a later
command fails in MacPort's sqlite package registry database, "attempt
to write a readonly database". At a wild guess, what has changed here
to trigger this new condition is that MacPorts has noticed a new
stable release of itself available and taken some new code path
related to upgrading. No idea why it thinks its package database is
read-only, though... looking...
From | Date | Subject | |
---|---|---|---|
Next Message | Alexander Korotkov | 2024-08-18 22:24:02 | Re: Add SPLIT PARTITION/MERGE PARTITIONS commands |
Previous Message | Thomas Munro | 2024-08-18 20:02:00 | Re: CI cpluspluscheck failures |