buildfarm + meson - Mailing list pgsql-hackers

From Andrew Dunstan
Subject buildfarm + meson
Date
Msg-id 5ee4ba57-d917-6785-8afa-a11f2c48fd55@dunslane.net
Whole thread Raw
Responses Re: buildfarm + meson
Re: buildfarm + meson
List pgsql-hackers

Here's a progress report on adapting the buildfarm client to meson

There is a development branch where I'm working on the changes. They can be seen here:

<https://github.com/PGBuildFarm/client-code/compare/main...dev/meson>

On my Linux box (Fedora 37, where crake runs) I can get a complete run. There is work to do to make sure we pick up the right log files, and maybe adjust a module or two. I have adopted a design where instead of trying to know a lot about the testing regime the client needs to know a lot less. Instead, it gets meson to tell it the set of tests. I will probably work on enabling some sort of filter, but I think this makes things more future-proof. I have stuck with the design of making testing fairly fine-grained, so each suite runs separately.

On a Windows instance, fairly similar to what's running drongo, I can get a successful build with meson+VS2019, but I'm getting an error in the regression tests, which don't like setting lc_time to 'de_DE'. Not sure what's going on there.

meson apparently wants touch and cp installed, although I can't see why at first glance. For Windows I just copied them into the path from an msys2 installation.


cheers


andrew

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

pgsql-hackers by date:

Previous
From: Zheng Li
Date:
Subject: Re: Support logical replication of DDLs
Next
From: Jim Jones
Date:
Subject: Re: [PATCH] Add pretty-printed XML output option