Re: issue with meson builds on msys2

On 2023-05-04 Th 19:54, Andres Freund wrote:
> 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?

Its a Windows Server 2019 (v 1809) instance running on AWS.

Here's an extract from systeminfo:

OS Name:                   Microsoft Windows Server 2019 Datacenter
OS Version:                10.0.17763 N/A Build 17763
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Standalone Server
OS Build Type:             Multiprocessor Free
Registered Owner:          EC2
Registered Organization:   Amazon.com
Product ID:                00430-00000-00000-AA796
Original Install Date:     4/24/2023, 10:28:31 AM
System Boot Time:          4/24/2023, 1:49:59 PM
System Manufacturer:       Amazon EC2
System Model:              t3.large
System Type:               x64-based PC
Processor(s):              1 Processor(s) Installed.
                           [01]: Intel64 Family 6 Model 85 Stepping 7
GenuineIntel ~2500 Mhz
BIOS Version:              Amazon EC2 1.0, 10/16/2017
Windows Directory:         C:\Windows
System Directory:          C:\Windows\system32
Boot Device:               \Device\HarddiskVolume1
System Locale:             en-us;English (United States)
Input Locale:              en-us;English (United States)
Time Zone:                 (UTC) Coordinated Universal Time
Total Physical Memory:     8,090 MB
Available Physical Memory: 4,843 MB
Virtual Memory: Max Size:  10,010 MB
Virtual Memory: Available: 7,405 MB
Virtual Memory: In Use:    2,605 MB

>
> 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...
>

Just to reassure myself I have not been hallucinating, I repeated the test.

pgrunner(at)EC2AMAZ-GCB871B UCRT64 ~/bf/root/HEAD/inst
$ /usr/bin/perl -e 'system(qq{"bin/pg_ctl" -D data-C -w -l logfile start
> startlog 2>&1}) ; print $? ? "BANG: $?\n" : "OK\n";'
OK

pgrunner(at)EC2AMAZ-GCB871B UCRT64 ~/bf/root/HEAD/inst
$ /usr/bin/perl -e 'system(qq{"bin/pg_ctl" -D data-C -w -l logfile stop
> stoplog 2>&1}) ; print $? ? "BANG: $?\n" : "OK\n";'
BANG: 33280

If you want to play I can arrange access.

cheers

andrew

--
Andrew Dunstan
EDB:https://www.enterprisedb.com