Re: tests and meson - test names and file locations - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: tests and meson - test names and file locations
Date
Msg-id 8bee9f84-63b0-5f45-dac6-767b66d630c5@dunslane.net
Whole thread Raw
In response to Re: tests and meson - test names and file locations  (Andres Freund <andres@anarazel.de>)
List 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@dunslane.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




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: tests and meson - test names and file locations
Next
From: "Jonathan S. Katz"
Date:
Subject: Re: SQL/JSON features for v15