From: David Gibson <david@gibson.dropbear.id.au>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: pbonzini@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] .travis.yml: migrate to container builds
Date: Wed, 20 Jan 2016 13:29:20 +1100 [thread overview]
Message-ID: <20160120022920.GI27454@voom.redhat.com> (raw)
In-Reply-To: <87fuxuc9uo.fsf@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 2574 bytes --]
On Tue, Jan 19, 2016 at 07:22:07AM +0000, Alex Bennée wrote:
>
> David Gibson <david@gibson.dropbear.id.au> 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 <alex.bennee@linaro.org>
> >
> > Tested-by: David Gibson <david@gibson.dropbear.id.au>
> >
> > 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.
Ok, but would it work to explicitly disable use of the packages in
some of the builds?
> > [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
Ah, ok. I'm kind of surprised that Travis passes a build requesting a
non-whitelisted package.
Do we want to wait until that's approved before merging? I don't have
a strong opinion either way.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-01-20 2:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-15 10:45 [Qemu-devel] [PATCH] .travis.yml: migrate to container builds Alex Bennée
2016-01-19 6:15 ` David Gibson
2016-01-19 7:22 ` Alex Bennée
2016-01-20 2:29 ` David Gibson [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160120022920.GI27454@voom.redhat.com \
--to=david@gibson.dropbear.id.au \
--cc=alex.bennee@linaro.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.