On Tue, Jan 19, 2016 at 03:00:52PM -0800, Junio C Hamano wrote: > Jeff King <peff@xxxxxxxx> writes: > > > On Tue, Jan 19, 2016 at 10:24:29AM +0100, larsxschneider@xxxxxxxxx wrote: > > > >> From: Lars Schneider <larsxschneider@xxxxxxxxx> > >> > >> Use the Travis-CI cache feature to store prove test results and make them > >> available in subsequent builds. This allows to run previously failed tests > >> first and run remaining tests in slowest to fastest order. As a result it > >> is less likely that Travis-CI needs to wait for a single test at the end > >> which speeds up the test suite execution by ~2 min. > > > > Thanks, this makes sense, and the patch looks good. > > > >> @@ -18,7 +22,7 @@ env: > >> - P4_VERSION="15.2" > >> - GIT_LFS_VERSION="1.1.0" > >> - DEFAULT_TEST_TARGET=prove > >> - - GIT_PROVE_OPTS="--timer --jobs 3" > >> + - GIT_PROVE_OPTS="--timer --jobs 3 --state=failed,slow,save" > > > > Have you tried bumping --jobs here? I usually use "16" on my local box. > > I think 3 comes from this: > > http://thread.gmane.org/gmane.comp.version-control.git/279348/focus=279674 Having recently looked into this, the relevant travis-ci documentation is: https://docs.travis-ci.com/user/ci-environment/ which says all environments have 2 cores, so you won't get much from anything higher than -j3. The following document also says something slightly different: https://docs.travis-ci.com/user/speeding-up-the-build#Parallelizing-your-build-on-one-VM "Travis CI VMs run on 1.5 virtual cores." > > I also looked into the Travis "container" thing. It's not clear to me > > from their page: > > > > https://docs.travis-ci.com/user/workers/container-based-infrastructure/ > > > > whether we're using the new, faster container infrastructure or not. > > ... > > depends on when Travis "recognized" the repo, but I'm not quite sure > > what that means. Should we be adding "sudo: false" to the top-level of > > the yaml file? > > In an earlier discussion > > http://thread.gmane.org/gmane.comp.version-control.git/279348/focus=279495 > > I found that we were not eligible for container-based sandbox as the > version of travis-yaml back then used "sudo". I do not seem to find > the use of sudo in the recent one we have in my tree, so it would be > beneficial if somebody interested in Travis CI look into this. The https://docs.travis-ci.com/user/ci-environment/ document says the default is "sudo: false" for repositories enabled in 2015 or later, which I assume is the case for the git repository. "sudo: required" is the default for repositories enabled before 2015. Mike -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html