Hi, On Mon, 13 Oct 2025 at 18:49, Dave Page <[email protected]> wrote: > > On Mon, 13 Oct 2025 at 15:57, Nazir Bilal Yavuz <[email protected]> wrote: >> >> I tested Meson 1.8.5 on the Postgres CI (on both VS 2019 and VS 2022), >> and there were no errors [1]. Also, Postgres CI uses Meson 1.9.1 >> without any failures. Could it be that one of the dependencies you >> build is causing the problem? >> >> [1] https://cirrus-ci.com/build/4701538502836224 > > > It seems unlikely to be another dependency, as the only variable being > changed is the Meson version. I just tried with 1.9.1 (not sure why new > releases.io didn't alert me to 1.9.x), and that appears to fail in the same > way. > > I do notice that the result of postgresql:setup (the first - and failing - > test, and I'd wager the cause of the following failures) is logged as: > > result: (exit status 3221225495 or signal 3221225367 SIGinvalid) > > I don't get any Google hits for the latter, but the former seems to indicate > an out of memory issue. That seems unlikely though, as Github apparently give > 16GB to the runners for public repos, which I'd expect to be enough. What do > you have on the Windows ones? The Cirrus website doesn't seem to list Windows > ones, so I'm guessing these are private runners in Azure?
They have 4 CPUs and 4 GB memory. These VMs are run on Google Cloud as custom Cirrus CI VMs [1]. Their specifications are set in the .cirrus.task.yml file and you can see the resource information on the Cirrus CI's task page (first entry on the environment variables section). [1] https://cirrus-ci.org/guide/custom-vms/#custom-compute-engine-vms -- Regards, Nazir Bilal Yavuz Microsoft
