Re: Adding CI to our tree - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: Adding CI to our tree
Date
Msg-id 1e7aaaf2-a17f-0718-a2e2-a0bd0f69f56b@dunslane.net
Whole thread Raw
In response to Re: Adding CI to our tree  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
Responses Re: Adding CI to our tree
List pgsql-hackers
On 1/18/22 08:06, Peter Eisentraut wrote:
> On 17.01.22 22:13, Andrew Dunstan wrote:
>> Well, the logic we use for TAP tests is we run them for the following if
>> they have a t subdirectory, subject to configuration settings like
>> PG_TEST_EXTRA:
>>
>>   src/test/bin/*
>>   contrib/*
>>   src/test/modules/*
>>   src/test/*
>>
>> As long as any new TAP test gets place in such a location nothing new is
>> required in the buildfarm client.
>
> But if I wanted to add TAP tests to libpq, then I'd still be stuck. 
> Why not change the above list to "anywhere"?



Sure, very doable, although we will still need some special logic for
src/test - there are security implication from running the ssl, ldap and
kerberos tests by default. See its Makefile.


cheers


andrew

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




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: a misbehavior of partition row movement (?)
Next
From: Joshua Brindle
Date:
Subject: Re: Support for NSS as a libpq TLS backend