Re: [HACKERS] Need a builtin way to run all tests faster manner - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [HACKERS] Need a builtin way to run all tests faster manner
Date
Msg-id 18710.1489288447@sss.pgh.pa.us
Whole thread Raw
In response to Re: [HACKERS] Need a builtin way to run all tests faster manner  (Andres Freund <andres@anarazel.de>)
Responses Re: [HACKERS] Need a builtin way to run all tests faster manner  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
Andres Freund <andres@anarazel.de> writes:
> On 2017-03-11 11:48:31 -0800, Andres Freund wrote:
>> I think that'd be a good plan.  We probably should also keep --outputdir
>> seperate (which test_decoding/Makefile does, but
>> pg_isolation_regress_check doesn't)?

> Here's a patch doing that (based on yours).  I'd be kind of inclined to
> set --outputdir for !isolation tests too; possibly even move tmp_check
> below output_iso/ output_regress/ or such - but that seems like it
> potentially could cause some disagreement...

This looks generally sane to me, although I'm not very happy about folding
the "$(MKDIR_P) output_iso" call into pg_isolation_regress_check --- that
seems weird and unlike the way it's done for the regular regression test
case.  But probably Peter has a better-informed opinion.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: [HACKERS] src/test/regress's check-prepared-txns target
Next
From: Robert Haas
Date:
Subject: Re: [HACKERS] \if, \elseif, \else, \endif (was Re: PSQL commands:\quit_if, \quit_unless)