Re: [PATCH v3 1/3] Add Travis CI support
- From
Lars Schneider <larsxschneider@gmail.com>
- Date
- Oct 15, 2015, 10:35 UTC
- Message-ID
- <F501FD44-F14B-4902-9E24-149451804C1C@gmail.com>
- In-Reply-To
- <vpqwpuo35zo.fsf@grenoble-inp.fr>
On 15 Oct 2015, at 10:12, Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> wrote:
Show 12 quoted lines
> Lars Schneider <larsxschneider@gmail.com> writes: > >> I was reluctant to this because I feared problems. Especially while >> running tests in parallel. > > Isn't the point of using a CI tool to notice problems? ;-) > > More seriously, running tests in parallel shouldn't be a problem since > each test runs in its own directory with HOME set to this private > directory, so two diffent tests should not interfer. If there's an issue > with parallel tests, we probably prefer discovering them than avoiding > them.
OK. Great!
Show 8 quoted lines
>> make -j2 9min 11sec: >> https://travis-ci.org/larsxschneider/git/jobs/85478022 >> >> make 17min 20sec: >> https://travis-ci.org/larsxschneider/git/jobs/85432398 > > Since the tests are essentially IO-bound and not CPU-bound, it may even > make sense to use -j3 here.
Hehe you're right.
make -j3 6min 2sec https://travis-ci.org/larsxschneider/git/jobs/85497307
just for fun I tried a few more values and -j5 seems to be the best with 4min 27sec https://travis-ci.org/larsxschneider/git/jobs/85501015
-j6 is slower again. Do you see a reason not to use "-j5"?
Thanks, Lars