| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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 14:38:09 |
| Message-ID: | tlh4lj6vvllkhxx3ve63j66fi5neaqasdnrk5ovfefwffbmx5n@eblyowi2z4j5 |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 2025-08-23 10:17:59 -0400, Tom Lane wrote:
> Andres Freund <andres(at)anarazel(dot)de> writes:
> > On 2025-08-23 11:57:37 +0500, Andrey Borodin wrote:
> >> What is the downside of the approach where meson uses t/*.pl wildcard?
>
> > In meson you can't do wildcards at "configure" time, since wildcards do not
> > allow reliable detection of when re-configure is needed.
>
> But ... what "re-configuration" is needed when adding a new test file?
In meson, not autoconf/make. The test runner doesn't parse the meson.build
files, that's done once when running configure. After that there's a table of
tests that need to be run that gets used when you type ninja/meson test.
> We should be striving to make the meson system as easy to use as
> autoconf/make, not trying to attain parity by making the latter experience
> worse.
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.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Noah Misch | 2025-08-23 14:45:05 | Re: Test instability when pg_dump orders by OID |
| Previous Message | Nathan Bossart | 2025-08-23 14:36:07 | Re: vacuumdb --missing-stats-only and permission issue |