Paolo Bonzini <pbonz...@redhat.com> writes: > On 14/07/2017 12:05, Alex Bennée wrote: >> >> Paolo Bonzini <pbonz...@redhat.com> writes: >> >>> docker-travis is limited to the -j3 flag specified for running on the >>> SaaS Travis CI infrastructure. >>> >>> When running the test matrix locally with docker, however, we can run >>> much more jobs at the same time on a suitably beefy server. Let people >>> do that with the usual J=nn option already supported by the other >>> docker-based tests. >> >> Eh, I was debugging stuff on our beefy server with J=20 and then I >> realised I was just running: >> >> make docker-test-quick@travis J=20 >> >> So I guess some people do use the pseudo Travis expansion then? > > How would that end up running tests/docker/travis?
It runs the normal build and make check but in the Travis build environment. Essentially the .travis.yml is just a bunch of alternative configure invocations, there is nothing to stop you manually setting up a build with TARGET_LIST and EXTRA_CONFIGURE_OPTS which is what I do if there is a particular Travis test which is failing. > > Paolo > >>> >>> Paolo >>> >>> Paolo Bonzini (2): >>> docker: allow customizing Travis global_env variables >>> travis: move make -j flag out of script >>> >>> .travis.yml | 3 ++- >>> tests/docker/travis.py | 6 +++--- >>> 2 files changed, 5 insertions(+), 4 deletions(-) >> >> >> -- >> Alex Bennée >> -- Alex Bennée
