From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql: Enforce our convention about max number of parallel regression t |
Date: | 2017-10-07 21:20:16 |
Message-ID: | E1e0wW8-0007xp-Mv@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Enforce our convention about max number of parallel regression tests.
We have a very old rule that parallel_schedule should have no more
than twenty tests in any one parallel group, so as to provide a
bound on the number of concurrently running processes needed to
pass the tests. But people keep forgetting the rule, so let's add
a few lines of code to check it.
Discussion: https://postgr.es/m/a37e9c57-22d4-1b82-1270-4501cd2e984e@2ndquadrant.com
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/ef73a8162a5fe9c4b2f895bf9fb660f1aabc796c
Modified Files
--------------
src/test/regress/GNUmakefile | 2 +-
src/test/regress/pg_regress.c | 25 ++++++++++++++++++++-----
src/tools/msvc/vcregress.pl | 2 ++
3 files changed, 23 insertions(+), 6 deletions(-)
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2017-10-07 22:04:32 | pgsql: Improve pg_regress's error reporting for schedule-file problems. |
Previous Message | Tom Lane | 2017-10-07 17:19:20 | pgsql: Clean up sloppy maintenance of regression test schedule files. |