Hi,
On 2023-05-03 09:20:28 -0400, Andrew Dunstan wrote:
> On 2023-04-27 Th 18:18, Andres Freund wrote:
> > On 2023-04-26 09:59:05 -0400, Andrew Dunstan wrote:
> > > Still running into this, and I am rather stumped. This is a blocker for
> > > buildfarm support for meson:
> > >
> > > Here's a simple illustration of the problem. If I do the identical test with
> > > a non-meson build there is no problem:
> > This happens 100% reproducible?
>
> For a sufficiently modern installation of msys2 (20230318 version) this is
> reproducible on autoconf builds as well.
>
> For now it's off my list of meson blockers. I will pursue the issue when I
> have time, but for now the IPC::Run workaround is sufficient.
Hm. I can't reproduce this in my test win10 VM, unfortunately. What OS / OS
version is the host? Any chance to get systeminfo.exe output or something like
that?
I think we ought to do something here. If newer environments cause failures
like this, it seems likely that this will spread to more and more applications
over time...
Greetings,
Andres Freund