[redirecting to -hackers]
On 2023-04-20 Th 15:37, Andrew Dunstan wrote:
On 2023-04-20 Th 11:06, Andres Freund wrote:
On 2023-04-17 16:22:30 -0400, Andrew Dunstan wrote:
I am still having Windows issues with meson, but only with MSYS2.
Any more details on that? I might be able to help out / improve things.
For some reason which makes no sense to me the buildfarm animal fails at the first Stop-Db step. The DB is actually stopped, but pg_ctl returns a non-zero status. The thing that's really odd is that meson isn't at all involved in this step. But it's happened enough that I've had to back off using meson builds on fairywren - I'm going to do more testing on a new Windows instance.
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:
pgrunner@EC2AMAZ-GCB871B UCRT64 ~/bf
$ export PGCTLTIMEOUT=300
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 start") ; print "fail\n" if $?; '
waiting for server to start.... done
server started
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") ; print "fail\n" if $?; '
waiting for server to shut down....fail
pgrunner@EC2AMAZ-GCB871B UCRT64 ~/bf
$ tail root/HEAD/instkeep.2023-04-25_11-09-41/logfile
2023-04-26 12:44:50.188 UTC [5132:2] LOG: listening on Unix socket "C:/tools/msys64/tmp/buildfarm-jaWBkm/.s.PGSQL.5678"
2023-04-26 12:44:50.249 UTC [5388:1] LOG: database system was shut down at 2023-04-26 12:43:02 UTC
2023-04-26 12:44:50.260 UTC [5132:3] LOG: database system is ready to accept connections
2023-04-26 12:45:01.542 UTC [5132:4] LOG: received fast shutdown request
2023-04-26 12:45:01.542 UTC [5132:5] LOG: aborting any active transactions
2023-04-26 12:45:01.547 UTC [5132:6] LOG: background worker "logical replication launcher" (PID 3876) exited with exit code 1
2023-04-26 12:45:01.550 UTC [6032:1] LOG: shutting down
2023-04-26 12:45:01.551 UTC [6032:2] LOG: checkpoint starting: shutdown immediate
2023-04-26 12:45:01.557 UTC [6032:3] LOG: checkpoint complete: wrote 2 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.003 s, sync=0.001 s, total=0.007 s; sync files=0, longest=0.000 s, average=0.000 s; distance=0 kB, estimate=0 kB; lsn=0/1034E7F8, redo lsn=0/1034E7F8
2023-04-26 12:45:01.568 UTC [5132:7] LOG: database system is shut down
cheers
andrew
--
Andrew Dunstan
EDB: https://www.enterprisedb.com