Re: Build failure with Meson >= 1.8.3 on Windows
| От | Dave Page |
|---|---|
| Тема | Re: Build failure with Meson >= 1.8.3 on Windows |
| Дата | |
| Msg-id | CA+OCxoxsb12HUMytCtswLhfp8LXvqS3kd3PMph78heqvDuFqVw@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Build failure with Meson >= 1.8.3 on Windows (Nazir Bilal Yavuz <byavuz81@gmail.com>) |
| Ответы |
Re: Build failure with Meson >= 1.8.3 on Windows
|
| Список | pgsql-hackers |
Hi
On Mon, 13 Oct 2025 at 15:57, Nazir Bilal Yavuz <byavuz81@gmail.com> wrote:
Hi,
On Mon, 13 Oct 2025 at 15:30, Dave Page <dpage@pgadmin.org> wrote:
>
> I recently tried to update the version of Meson used in my winpgbuild project, which builds PostgreSQL for Windows, along with (almost) all the various dependencies. Something has changed in versions from 1.8.3 and above which causes the regression tests to fail:
>
> This successful run is with Meson 1.8.2: https://github.com/dpage/winpgbuild/actions/runs/18462942864
>
> This failed run is with Meson 1.8.3: https://github.com/dpage/winpgbuild/actions/runs/18464267466
>
> This failed run is with Meson 1.8.5: https://github.com/dpage/winpgbuild/actions/runs/18456020620
>
> Logs etc. can be found at the URLs above (you might need to be logged into Github to see them); I haven't attached them here as they will almost certainly exceed the size limit for the mailing list.
>
> We do have 3 build farm animals running Meson, however they all have significantly older versions installed.
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?
Dave Page
pgAdmin: https://www.pgadmin.org
PostgreSQL: https://www.postgresql.org
В списке pgsql-hackers по дате отправления: