From: Matthieu Moy Date: Thu, 15 Oct 2015 08:12:27 GMT Subject: Re: [PATCH v3 1/3] Add Travis CI support Message-ID: In-Reply-To: <14146E1E-857D-416B-9287-F20826DCB806@gmail.com> Lars Schneider 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. > 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. -- Matthieu Moy http://www-verimag.imag.fr/~moy/