Re: [HACKERS] TAP tests take a long time - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [HACKERS] TAP tests take a long time
Date
Msg-id 748.1491940354@sss.pgh.pa.us
Whole thread Raw
In response to Re: [HACKERS] TAP tests take a long time  (Andrew Dunstan <andrew.dunstan@2ndquadrant.com>)
Responses Re: [HACKERS] TAP tests take a long time
List pgsql-hackers
Andrew Dunstan <andrew.dunstan@2ndquadrant.com> writes:
>> The other thing that might be useful here is to push on parallelizing
>> buildfarm runs.

> One reason I haven't supported "make -j nn" everywhere (it is supported
> for making core, contrib and test_modules) is that the output tends to
> get rather jumbled, and I didn't want to impose that extra burden in
> people trying to decipher the results.

Agreed, that would be a mess.  I was thinking in terms of running steps in
parallel if they have independent output log files, so that that problem
wouldn't arise.  AFAIK, for example, we could run the per-subdirectory
"make check" tests in src/bin/ in parallel without incurring any
legibility issues.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] Possible problem in Custom Scan API
Next
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] SCRAM authentication, take three