From: Andrew Dunstan <andrew@dunslane.net>
To: Andres Freund <andres@anarazel.de>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@lists.postgresql.org
Subject: Re: issue with meson builds on msys2
Date: Fri, 5 May 2023 07:08:39 -0400
Message-ID: <2ff71af4-cdee-37b8-525a-2b25afd1769a@dunslane.net> (raw)
In-Reply-To: <20230504235413.eibaxlxslo76ipjl@awork3.anarazel.de>
References: <E1poQg3-003Xv9-UZ@gemulon.postgresql.org>
<08dd6053-deee-52e9-954b-eb69232905c9@dunslane.net>
<2506819.1681761221@sss.pgh.pa.us>
<7d7dcc20-ba19-5340-9be8-f255e8b42edc@dunslane.net>
<20230420150652.jciazjap223iznjp@awork3.anarazel.de>
<5bddd941-9819-6655-7a71-3f346050583e@dunslane.net>
<6efeb45a-07f9-2291-c8f8-9fb4abbb6ebc@dunslane.net>
<20230427221828.2qo7z4xb4f7islln@awork3.anarazel.de>
<236c0354-62b1-0ae1-a252-4c866bc1c5d6@dunslane.net>
<20230504235413.eibaxlxslo76ipjl@awork3.anarazel.de>
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@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@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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-committers@postgresql.org
Cc: andrew@dunslane.net, andres@anarazel.de, tgl@sss.pgh.pa.us, pgsql-hackers@lists.postgresql.org
Subject: Re: issue with meson builds on msys2
In-Reply-To: <2ff71af4-cdee-37b8-525a-2b25afd1769a@dunslane.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox