From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:51697) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aLQcI-0005zV-EE for qemu-devel@nongnu.org; Tue, 19 Jan 2016 02:22:15 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aLQcE-0008Fv-Bz for qemu-devel@nongnu.org; Tue, 19 Jan 2016 02:22:14 -0500 Received: from mail-wm0-x22b.google.com ([2a00:1450:400c:c09::22b]:37434) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aLQcE-0008Fp-60 for qemu-devel@nongnu.org; Tue, 19 Jan 2016 02:22:10 -0500 Received: by mail-wm0-x22b.google.com with SMTP id n5so96767365wmn.0 for ; Mon, 18 Jan 2016 23:22:10 -0800 (PST) References: <1452854709-12855-1-git-send-email-alex.bennee@linaro.org> <20160119061505.GC27454@voom.redhat.com> From: Alex =?utf-8?Q?Benn=C3=A9e?= In-reply-to: <20160119061505.GC27454@voom.redhat.com> Date: Tue, 19 Jan 2016 07:22:07 +0000 Message-ID: <87fuxuc9uo.fsf@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Subject: Re: [Qemu-devel] [PATCH] .travis.yml: migrate to container builds List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: David Gibson Cc: pbonzini@redhat.com, qemu-devel@nongnu.org David Gibson writes: > On Fri, Jan 15, 2016 at 10:45:09AM +0000, Alex Bennée wrote: >> This moves the Travis tests from their old legacy VM >> infrastructure (which only seems to run 5-6 jobs at once) to their new >> container based approach. >> >> The principle difference is there is no sudo in the containers so all >> packages are installed using the apt add-on. This means one of the build >> combinations can be dropped as it was only for checking the build with >> additional packages. >> >> I've disabled the user-space tracing build until the dependant packages >> go through the Travis package white-listing process. >> >> Signed-off-by: Alex Bennée > > Tested-by: David Gibson > > Is it safe to just drop that build combination, or should we instead > be doing something else to test the build _without_ those extra > packages? Hmm, currently there doesn't seem to be a way to do this with the Travis infrastructure as the packages are no longer part of a matrix. > > > [snip] >> @@ -86,10 +103,10 @@ matrix: >> - env: TARGETS=i386-softmmu,x86_64-softmmu >> EXTRA_CONFIG="--enable-trace-backends=ftrace" >> compiler: gcc >> - - env: TARGETS=i386-softmmu,x86_64-softmmu >> - EXTRA_PKGS="liblttng-ust-dev liburcu-dev" >> - EXTRA_CONFIG="--enable-trace-backends=ust" >> - compiler: gcc >> + # UST backend disabled until liblttng-ust-dev pkg white-listed >> + #- env: TARGETS=i386-softmmu,x86_64-softmmu >> + # EXTRA_CONFIG="--enable-trace-backends=ust" >> + # compiler: gcc > > This comment is a bit confusing to me, since the apt addon package > list already seems to include liblttng-ust-dev. It's in the list but still awaiting whitelisting by Travis: https://github.com/travis-ci/apt-package-whitelist/issues/2258 > >> - env: TARGETS=i386-softmmu,x86_64-softmmu >> EXTRA_CONFIG="--enable-modules" >> compiler: gcc -- Alex Bennée