All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: pbonzini@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] .travis.yml: migrate to container builds
Date: Tue, 19 Jan 2016 07:22:07 +0000	[thread overview]
Message-ID: <87fuxuc9uo.fsf@linaro.org> (raw)
In-Reply-To: <20160119061505.GC27454@voom.redhat.com>


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.

>
>
> [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

  reply	other threads:[~2016-01-19  7:22 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 [this message]
2016-01-20  2:29     ` David Gibson

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=87fuxuc9uo.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=david@gibson.dropbear.id.au \
    --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.