Re: [PATCH v3 1/3] Add Travis CI support
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- Oct 15, 2015, 10:50 UTC
- Message-ID
- <alpine.DEB.1.00.1510151247550.31610@s15462909.onlinehome-server.info>
- In-Reply-To
- <vpqwpuo35zo.fsf@grenoble-inp.fr>
Hi,
On Thu, 15 Oct 2015, Matthieu Moy 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.
I vividly remember pulling my hair out over BuildHive (i.e. the Java-based Jenkins alternative to Travis) failures that turned out to be resource-related: I simply overloaded the BuildHive node.
So I assumed that the problems Lars referred to would not be problems of Git, or the test suite, but of overwhelming a free service with an unreasonable load.
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.
I would like to caution against overloading Travis. They are really nice to us, we should try to be nice to them, too.
Ciao, Dscho