Re: Adding CI to our tree

From: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>, Andres Freund <andres(at)anarazel(dot)de>
Cc: Justin Pryzby <pryzby(at)telsasoft(dot)com>, pgsql-hackers(at)postgresql(dot)org, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Melanie Plageman <melanieplageman(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Daniel Gustafsson <daniel(at)yesql(dot)se>
Subject: Re: Adding CI to our tree
Date: 2022-01-18 13:06:18
Message-ID: 988efcb9-52fe-e011-3661-f8f8b4e3d8c3@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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"?

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2022-01-18 13:24:34 Re: missing indexes in indexlist with partitioned tables
Previous Message Peter Eisentraut 2022-01-18 12:54:50 Re: ICU for global collation