From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: TAP tests take a long time |
Date: | 2017-04-11 19:52:34 |
Message-ID: | 748.1491940354@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2017-04-11 19:55:37 | Re: SCRAM authentication, take three |
Previous Message | Tom Lane | 2017-04-11 19:47:50 | Re: Possible problem in Custom Scan API |