From: "Alex Bennée" <alex.bennee@linaro.org>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] travis: trim out most clang builds
Date: Fri, 04 Nov 2016 16:40:09 +0000 [thread overview]
Message-ID: <87k2cjtd06.fsf@linaro.org> (raw)
In-Reply-To: <20161027132345.21072-1-berrange@redhat.com>
Daniel P. Berrange <berrange@redhat.com> writes:
> We test with both gcc and clang in order to detect cases
> where clang issues warnings that gcc misses. To achieve
> this though we don't need to build QEMU in multiple
> different configurations. Just a single clang-on-linux
> build will be sufficient, if we have an "all enabled"
> config.
>
> This cuts the number of build jobs from 21 to 16,
> reducing the load imposed on shared Travis CI infra.
> This will make it practical to enable jobs for other
> interesting & useful configurations without DOS'ing
> Travis to much.
>
> Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
> ---
> .travis.yml | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/.travis.yml b/.travis.yml
> index 9916178..0706b9a 100644
> --- a/.travis.yml
> +++ b/.travis.yml
> @@ -4,7 +4,6 @@ python:
> - "2.4"
> compiler:
> - gcc
> - - clang
> cache: ccache
> addons:
> apt:
> @@ -68,6 +67,9 @@ script:
> - make -j3 && ${TEST_CMD}
> matrix:
> include:
> + # Test with CLang for compile portability
> + - env: CONFIG=""
> + compiler: clang
> # gprof/gcov are GCC features
> - env: CONFIG="--enable-gprof --enable-gcov --disable-pie"
> compiler: gcc
Good idea. I'll add it to my tree.
Thanks.
--
Alex Bennée
prev parent reply other threads:[~2016-11-04 16:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-27 13:23 [Qemu-devel] [PATCH] travis: trim out most clang builds Daniel P. Berrange
2016-11-04 12:52 ` Stefan Hajnoczi
2016-11-04 16:40 ` Alex Bennée [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=87k2cjtd06.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=berrange@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.