Re: List TAP test files in makefiles

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, Peter Eisentraut <peter(at)eisentraut(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: List TAP test files in makefiles
Date: 2025-08-23 16:11:51
Message-ID: 2274949.1755965511@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andres Freund <andres(at)anarazel(dot)de> writes:
> FWIW, I find the autoconf/make test run experience completely unusable. It
> literally is made me embark on getting away from it. I don't understand how
> people stand it.

Interesting perspective, because from where I sit the testing aspect
is the weakest part of our meson setup: it seems to be very much
all-or-nothing, whereas the makefiles allow you to run any particular
test suite you want. Maybe this is just a lack of documentation?
There is still not a word in

https://www.postgresql.org/docs/devel/regress-run.html

about how to accomplish any of those effects under meson.

I find the lack of any equivalent to installcheck to be
particularly distressing, since it means you can't repeat
a test without paying for "make temp-install" every time.
Admittedly that doesn't work for a test that needs particular
non-default installation settings, but that's a minority
of our tests.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2025-08-23 16:16:25 Re: Changing gssencmode default in Psycopg
Previous Message Andrew Dunstan 2025-08-23 15:23:21 Re: List TAP test files in makefiles