Re: Need a builtin way to run all tests faster manner

Andrew Dunstan <andrew.dunstan@2ndquadrant.com>

From: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>, Andres Freund <andres@anarazel.de>
Cc: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>, Stephen Frost <sfrost@snowman.net>, pgsql-hackers@postgresql.org
Date: 2017-03-13T23:26:20Z
Lists: pgsql-hackers

On 03/13/2017 07:21 PM, Andrew Dunstan wrote:
>
> On 03/13/2017 12:35 AM, Tom Lane wrote:
>> Andres Freund <andres@anarazel.de> writes:
>>> On 2017-03-11 22:14:07 -0500, Tom Lane wrote:
>>>> 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.
>>> Yea, not super happy about that either - alternatively we could fold it
>>> into pg_regress.
>> Yeah, teaching pg_regress to auto-create the --temp-instance directory
>> seems perfectly sane from here.
>
> w.r.t. $subject, I thought it might be useful to get some recent stats
> from the buildfarm. Results are below. The bin checks dwarf everything
> else. Upgrade checks and isolation check are other items of significant
> cost. Upgrade checks could be significantly shortened if we could avoid
> rerunning the regression tests.


Sorry for line wrapping. Better formatted here:
<https://gist.github.com/adunstan/fbbdfe646427710233ecb67569665de9>

cheers

andrew

-- 
Andrew Dunstan                https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



Commits

  1. Improve isolation tests infrastructure.