From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: TAP tests, directories and parameters |
Date: | 2022-01-24 20:43:25 |
Message-ID: | 2139491.1643057005@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andres Freund <andres(at)anarazel(dot)de> writes:
> It's currently not possible to just run all tap tests in one prove run,
> because a number of tests assume that they are run from specific directories
> and/or with per-directory parameters.
> For meson I "solved" this by running each individual test in a wrapper that
> changes directory etc. But that's not really a great approach.
> To me it seems we should change our tests and test invocations to not depend
> on being run from a specific directory and to unify the environment variables
> passed to tap tests to one set somewhere central.
I'd be sad if this implied that running "make [install]check" in a
particular subdirectory no longer runs just that directory's tests.
Otherwise, sounds fine.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2022-01-24 20:48:21 | Re: Replace uses of deprecated Python module distutils.sysconfig |
Previous Message | Bossart, Nathan | 2022-01-24 20:40:08 | Re: Catalog version access |