Re: meson + libpq_pipeline

From: Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>
To: Tristan Partin <tristan(at)neon(dot)tech>
Cc: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Pg Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: meson + libpq_pipeline
Date: 2024-01-29 20:52:38
Message-ID: CAGECzQRzw5Mv=f5nxOoqYmEMAEoeCZmt2cr152MfMvXPQqsEqw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, 29 Jan 2024 at 19:37, Tristan Partin <tristan(at)neon(dot)tech> wrote:
>
> On Mon Jan 29, 2024 at 11:37 AM CST, Alvaro Herrera wrote:
> > I just realized while looking at Jelte's patch for the new nonblocking
> > query cancel stuff that the Meson build doesn't run the libpq_pipeline
> > tests :-(
> >
> > Is there any way to wire the tests to make it work?
>
> I can try to take a look for you. Not sure how hard it will be, but
> I can take a crack at it this week.

It already does afaik.

src/test/modules/libpq_pipeline/meson.build includes rules to execute
t/001_libpq_pipeline.pl

And to run a specific test I run the libpq_pipeline binary manually
against some postgres port that is already up:

ninja -C build && build/src/test/modules/libpq_pipeline/libpq_pipeline
cancel 'port=9700'

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Ants Aasma 2024-01-29 21:12:55 Re: Change GUC hashtable to use simplehash?
Previous Message Andres Freund 2024-01-29 20:38:50 Re: Should we remove -Wdeclaration-after-statement?