Re: tests and meson - test names and file locations

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: tests and meson - test names and file locations
Date: 2022-08-11 17:07:44
Message-ID: 8bee9f84-63b0-5f45-dac6-767b66d630c5@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 2022-08-11 Th 11:06, Andres Freund wrote:
> Hi,
>
> On 2022-08-11 10:20:42 -0400, Tom Lane wrote:
>> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>>> I also like that. I think we should take this opportunity for some
>>> serious rationalization of this. Tests and associated data have grown
>>> rather like Topsy, and we should fix that. So please don't feel too
>>> constrained by current practice.
>> I'm definitely -1 on that. Major rearrangement of the test scripts
>> would be a huge blocking factor for almost any back-patch. I don't
>> care much if you want to rearrange how the tests are invoked, but
>> please don't touch the individual .sql and .pl scripts.
> I don't precisely know what Andrew was thinking of, but the relocation of log
> files for example doesn't require many changes to .pl files - one change to
> Utils.pm. The one exception to that is 010_tab_completion.pl, which encodes
> tmp_check/ in its output.

I meant test results, logs et. I thought that was the topic under
discussion. Changing the location of test sources would be a whole other
topic. Sorry if I was not clear enough.

cheers

andrew

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jonathan S. Katz 2022-08-11 17:08:03 Re: SQL/JSON features for v15
Previous Message Tom Lane 2022-08-11 17:06:35 Re: tests and meson - test names and file locations