Re: Cirrus CI for macOS branches 16 and 15 broken
Thomas Munro <thomas.munro@gmail.com>
From: Thomas Munro <thomas.munro@gmail.com>
To: Peter Eisentraut <peter@eisentraut.org>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2024-08-18T22:01:55Z
Lists: pgsql-hackers
On Mon, Aug 19, 2024 at 7:52 AM Thomas Munro <thomas.munro@gmail.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...
Commits
-
ci: Upgrade MacPorts version to 2.10.1.
- 4247575c637b 15.9 landed
- 1553c84960b0 16.5 landed
- 4b6aa0cffc04 17.0 landed
- b10528e6cc67 18.0 landed