Re: issue with meson builds on msys2 - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: issue with meson builds on msys2
Date
Msg-id 365f59bd-1aaf-0af0-46ee-89e6a0dae391@dunslane.net
Whole thread Raw
In response to Re: issue with meson builds on msys2  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: issue with meson builds on msys2
List pgsql-hackers


On 2023-04-26 We 10:58, Tom Lane wrote:
I wrote:
Looking at the pg_ctl source code, the only way I can explain that
printout is that do_stop called wait_for_postmaster_stop which,
after one or more loops, exited via one of its exit() calls.
Ah, a little too hasty there: it's get_pgpid() that has to be
reaching an exit().



If I redirect the output to a file (which is what the buildfarm client actually does), it seems like it completes successfully, but I still get a non-zero exit:


pgrunner@EC2AMAZ-GCB871B UCRT64 ~/bf
$ /usr/bin/perl -e 'chdir "root/HEAD/instkeep.2023-04-25_11-09-41"; system("bin/pg_ctl -D data-C -l logfile stop > stoplog 2>&1") ; print "BANG\n" if $?; '
BANG

pgrunner@EC2AMAZ-GCB871B UCRT64 ~/bf
$ cat root/HEAD/instkeep.2023-04-25_11-09-41/stoplog
waiting for server to shut down.... done
server stopped


It seems more than odd that we get to where the "server stopped" massage is printed but we get a failure.


cheers


andrew

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

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: issue with meson builds on msys2
Next
From: Dimos Stamatakis
Date:
Subject: Re: Fix for visibility check on 14.5 fails on tpcc with high concurrency