On 2014-08-26 23:56:10 -0400, Peter Eisentraut wrote:
> On Tue, 2014-08-26 at 02:05 +0200, Andres Freund wrote:
> > Currently running "make -j16 all check" in contrib/ results in a mess
> > because
> > all pg_regress invocations fight over the same port. Adding a simple
> > .NOTPARALLEL: check-%-re
On Tue, 2014-08-26 at 02:05 +0200, Andres Freund wrote:
> Currently running "make -j16 all check" in contrib/ results in a mess
> because
> all pg_regress invocations fight over the same port. Adding a simple
> .NOTPARALLEL: check-%-recurse
> into contrib/Makefile fixes that. Do we want that?
But
On 2014-08-25 20:16:50 -0400, Tom Lane wrote:
> Andres Freund writes:
> > Currently running "make -j16 all check" in contrib/ results in a mess
> > because
> > all pg_regress invocations fight over the same port. Adding a simple
> > .NOTPARALLEL: check-%-recurse
> > into contrib/Makefile fixes th
Andres Freund writes:
> Currently running "make -j16 all check" in contrib/ results in a mess because
> all pg_regress invocations fight over the same port. Adding a simple
> .NOTPARALLEL: check-%-recurse
> into contrib/Makefile fixes that. Do we want that?
Dunno, but if we do, it should be appli
Hi,
Currently running "make -j16 all check" in contrib/ results in a mess because
all pg_regress invocations fight over the same port. Adding a simple
.NOTPARALLEL: check-%-recurse
into contrib/Makefile fixes that. Do we want that?
Greetings,
Andres Freund
--
Andres Freund
