Re: buildfarm + meson

On 2023-03-18 Sa 21:32, Andrew Dunstan wrote: On 2023-03-18 Sa 19:00, Andres Freund wrote: Hi, On 2023-03-18 17:53:38 -0400, Andrew Dunstan wrote: On 2023-03-11 Sa 16:25, Andres Freund wrote: Hi, On 2023-03-09 18:31:10 -0500, Andrew Dunstan wrote: Another thing: the test for uuid.h is

Re: buildfarm + meson

On 2023-03-18 Sa 19:00, Andres Freund wrote: Hi, On 2023-03-18 17:53:38 -0400, Andrew Dunstan wrote: On 2023-03-11 Sa 16:25, Andres Freund wrote: Hi, On 2023-03-09 18:31:10 -0500, Andrew Dunstan wrote: Another thing: the test for uuid.h is too strict. On Fedora 36 the OSSP header is in

Re: buildfarm + meson

Hi, On 2023-03-18 17:53:38 -0400, Andrew Dunstan wrote: > On 2023-03-11 Sa 16:25, Andres Freund wrote: > > Hi, > > > > On 2023-03-09 18:31:10 -0500, Andrew Dunstan wrote: > > > Another thing: the test for uuid.h is too strict. On Fedora 36 the OSSP > > > header is in /usr/include, not

Re: buildfarm + meson

On 2023-03-11 Sa 16:25, Andres Freund wrote: Hi, On 2023-03-09 18:31:10 -0500, Andrew Dunstan wrote: Another thing: the test for uuid.h is too strict. On Fedora 36 the OSSP header is in /usr/include, not /usr/include/ossp (I got around that for now by symlinking it, but obviously that's a

Re: buildfarm + meson

On 2023-03-10 Fr 18:05, Andres Freund wrote: Hi, On 2023-03-09 11:55:57 -0800, Andres Freund wrote: On 2023-03-09 14:47:36 -0500, Andrew Dunstan wrote: On 2023-03-09 Th 08:28, Andrew Dunstan wrote: At this stage I think I'm prepared to turn this loose on a couple of my buildfarm animals,

Re: buildfarm + meson

Hi, On 2023-03-09 18:31:10 -0500, Andrew Dunstan wrote: > Another thing: the test for uuid.h is too strict. On Fedora 36 the OSSP > header is in /usr/include, not /usr/include/ossp (I got around that for now > by symlinking it, but obviously that's a nasty hack we can't ask people to > do) Yea,

Re: buildfarm + meson

Hi, On 2023-03-09 11:55:57 -0800, Andres Freund wrote: > On 2023-03-09 14:47:36 -0500, Andrew Dunstan wrote: > > On 2023-03-09 Th 08:28, Andrew Dunstan wrote: > > > At this stage I think I'm prepared to turn this loose on a couple of my > > > buildfarm animals, and if nothing goes awry for the

Re: buildfarm + meson

On 2023-03-09 Th 14:47, Andrew Dunstan wrote: On 2023-03-09 Th 08:28, Andrew Dunstan wrote: At this stage I think I'm prepared to turn this loose on a couple of my buildfarm animals, and if nothing goes awry for the remainder of the month merge the dev/meson branch and push a new

Re: buildfarm + meson

On 2023-03-09 Th 15:25, Tom Lane wrote: Andres Freund writes: On 2023-03-09 14:47:36 -0500, Andrew Dunstan wrote: . There appears to be some mismatch in database names (e.g. regression_dblink vs contrib_regression_dblink). That's going to cause some issues with the module that adjusts things

Re: buildfarm + meson

Andres Freund writes: > On 2023-03-09 14:47:36 -0500, Andrew Dunstan wrote: >> . There appears to be some mismatch in database names (e.g. >> regression_dblink vs contrib_regression_dblink). That's going to cause some >> issues with the module that adjusts things for cross version upgrade. > I

Re: buildfarm + meson

Hi, On 2023-03-09 14:47:36 -0500, Andrew Dunstan wrote: > On 2023-03-09 Th 08:28, Andrew Dunstan wrote: > > At this stage I think I'm prepared to turn this loose on a couple of my > > buildfarm animals, and if nothing goes awry for the remainder of the > > month merge the dev/meson branch and

Re: buildfarm + meson

On 2023-03-09 Th 08:28, Andrew Dunstan wrote: At this stage I think I'm prepared to turn this loose on a couple of my buildfarm animals, and if nothing goes awry for the remainder of the month merge the dev/meson branch and push a new release. There is still probably a little polishing

Re: buildfarm + meson

On 2023-03-08 We 17:23, Andrew Dunstan wrote: On 2023-03-08 We 14:22, Andres Freund wrote: Hi, On 2023-03-02 17:35:26 -0500, Andrew Dunstan wrote: On 2023-03-02 Th 17:06, Andres Freund wrote: Hi On 2023-03-02 17:00:47 -0500, Andrew Dunstan wrote: On 2023-03-01 We 16:32, Andres Freund

Re: buildfarm + meson

On 2023-03-08 We 14:22, Andres Freund wrote: Hi, On 2023-03-02 17:35:26 -0500, Andrew Dunstan wrote: On 2023-03-02 Th 17:06, Andres Freund wrote: Hi On 2023-03-02 17:00:47 -0500, Andrew Dunstan wrote: On 2023-03-01 We 16:32, Andres Freund wrote: This is now working on my MSVC test rig

Re: buildfarm + meson

Hi, On 2023-03-02 17:35:26 -0500, Andrew Dunstan wrote: > On 2023-03-02 Th 17:06, Andres Freund wrote: > > Hi > > > > On 2023-03-02 17:00:47 -0500, Andrew Dunstan wrote: > > > On 2023-03-01 We 16:32, Andres Freund wrote: > > > > > This is now working > > > > > on my MSVC test rig (WS2019,

Re: buildfarm + meson

Hi, On 2023-03-08 09:41:57 -0500, Andrew Dunstan wrote: > On 2023-03-08 We 08:57, Andrew Dunstan wrote: > > On 2023-03-07 Tu 20:29, Andres Freund wrote: > > > On 2023-03-07 15:47:54 -0500, Andrew Dunstan wrote: > > > Here's a prototype for that. > > > > > > It adds an install-test-files target,

Re: buildfarm + meson

On 2023-03-08 We 08:57, Andrew Dunstan wrote: On 2023-03-07 Tu 20:29, Andres Freund wrote: Hi, On 2023-03-07 15:47:54 -0500, Andrew Dunstan wrote: On 2023-03-07 Tu 14:37, Andres Freund wrote: The failures are like this: +ERROR: extension "dummy_index_am" is not available +DETAIL: Could

Re: buildfarm + meson

Hi, On Wed, 8 Mar 2023 at 16:57, Andrew Dunstan wrote: > So if I understand this right, the way to use this would be something like: > > > local $ENV{DESTDIR} = $installdir; > > run_log("meson compile -C $pgsql install-test-files"); > > > Is that right? I did that but it didn't work :-(

Re: buildfarm + meson

On 2023-03-07 Tu 20:29, Andres Freund wrote: Hi, On 2023-03-07 15:47:54 -0500, Andrew Dunstan wrote: On 2023-03-07 Tu 14:37, Andres Freund wrote: The failures are like this: +ERROR: extension "dummy_index_am" is not available +DETAIL: Could not open extension control file

Re: buildfarm + meson

On 2023-03-07 18:26:21 -0800, Andres Freund wrote: > On 2023-02-23 06:27:23 -0500, Andrew Dunstan wrote: > > Yeah. For touch I think we can probably just get rid of this line in the > > root meson.build: > > > > touch = find_program('touch', native: true) > > Yep. > > > For cp there doesn't

Re: buildfarm + meson

Hi, On 2023-02-23 06:27:23 -0500, Andrew Dunstan wrote: > Yeah. For touch I think we can probably just get rid of this line in the > root meson.build: > > touch = find_program('touch', native: true) Yep. > For cp there doesn't seem to be a formal requirement, but there is a recipe > in

Re: buildfarm + meson

Hi, On 2023-03-07 15:47:54 -0500, Andrew Dunstan wrote: > On 2023-03-07 Tu 14:37, Andres Freund wrote: > > The failures are like this: > > > > +ERROR: extension "dummy_index_am" is not available > > +DETAIL: Could not open extension control file > >

Re: buildfarm + meson

On 2023-03-07 Tu 14:37, Andres Freund wrote: Hi, On 2023-03-01 13:32:58 -0800, Andres Freund wrote: On 2023-03-01 16:21:32 -0500, Andrew Dunstan wrote: Perhaps the latest version will be more to your taste. I'll check it out. A simple conversion from an existing config failed with: Can't

Re: buildfarm + meson

Hi, On 2023-03-01 13:32:58 -0800, Andres Freund wrote: > On 2023-03-01 16:21:32 -0500, Andrew Dunstan wrote: > > Perhaps the latest version will be more to your taste. > > I'll check it out. A simple conversion from an existing config failed with: Can't use an undefined value as an ARRAY

Re: buildfarm + meson

On 2023-03-02 Th 17:06, Andres Freund wrote: Hi On 2023-03-02 17:00:47 -0500, Andrew Dunstan wrote: On 2023-03-01 We 16:32, Andres Freund wrote: This is now working on my MSVC test rig (WS2019, VS2019, Strawberry Perl), including TAP tests. I do get a whole lot of annoying messages like

Re: buildfarm + meson

Hi On 2023-03-02 17:00:47 -0500, Andrew Dunstan wrote: > > On 2023-03-01 We 16:32, Andres Freund wrote: > > > This is now working > > > on my MSVC test rig (WS2019, VS2019, Strawberry Perl), including TAP > > > tests. > > > I do get a whole lot of annoying messages like this: > > > > > >

Re: buildfarm + meson

On 2023-03-01 We 16:32, Andres Freund wrote: This is now working on my MSVC test rig (WS2019, VS2019, Strawberry Perl), including TAP tests. I do get a whole lot of annoying messages like this: Unknown TAP version. The first line MUST be `TAP version `. Assuming version 12. The newest minor

Re: buildfarm + meson

Hi, On 2023-03-01 16:21:32 -0500, Andrew Dunstan wrote: > Perhaps the latest version will be more to your taste. I'll check it out. > This is now working > on my MSVC test rig (WS2019, VS2019, Strawberry Perl), including TAP tests. > I do get a whole lot of annoying messages like this: > >

Re: buildfarm + meson

On 2023-02-23 Th 10:58, Andres Freund wrote: On 2023-02-23 06:27:23 -0500, Andrew Dunstan wrote: On 2023-02-22 We 20:20, Andres Freund wrote: 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

Re: buildfarm + meson

On Fri, Feb 24, 2023 at 2:22 PM Andrew Dunstan wrote: > > On drongo, this test isn't failing, and I think the reason is that it runs > "make NO_LOCALE=1 check" so it never gets a database with win1252 encoding. > > I'm going to try adding a win1252 test to drongo's locales. > What seems to be

Re: buildfarm + meson

On 2023-02-23 Th 16:12, Andrew Dunstan wrote: On 2023-02-23 Th 10:58, Andres Freund wrote: 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

Re: buildfarm + meson

On 2023-02-23 Th 10:58, Andres Freund wrote: 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. Huh,

Re: buildfarm + meson

On 2023-02-23 06:27:23 -0500, Andrew Dunstan wrote: > > On 2023-02-22 We 20:20, Andres Freund wrote: > > > > > 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

Re: buildfarm + meson

On 2023-02-22 We 20:20, Andres Freund wrote: 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

Re: buildfarm + meson

On 2023-02-22 We 19:23, Michael Paquier wrote: 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. What's

Re: buildfarm + meson

Hi, On 2023-02-22 18:23:44 -0500, Andrew Dunstan wrote: > 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: > > >

Re: buildfarm + meson

On Wed, Feb 22, 2023 at 06:23:44PM -0500, Andrew Dunstan wrote: > 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

buildfarm + meson

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: On my Linux box (Fedora 37, where crake runs) I can get a complete