From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: issue with meson builds on msys2 |
Date: | 2023-04-26 15:11:33 |
Message-ID: | 365f59bd-1aaf-0af0-46ee-89e6a0dae391@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers 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(at)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(at)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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2023-04-26 15:30:22 | Re: issue with meson builds on msys2 |
Previous Message | Tom Lane | 2023-04-26 14:58:11 | Re: issue with meson builds on msys2 |
From | Date | Subject | |
---|---|---|---|
Next Message | Dimos Stamatakis | 2023-04-26 15:24:37 | Re: Fix for visibility check on 14.5 fails on tpcc with high concurrency |
Previous Message | Tom Lane | 2023-04-26 14:58:11 | Re: issue with meson builds on msys2 |