Skip to contentSkip to conversation

travis: trim out most clang builds

PATCH In review Daniel P. Berrange 3 participants 3 messages Oct 27, 2016 – Nov 4, 2016

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 travis: trim out most clang builds

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.

---
 .travis.yml | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)
.travis.yml +3 -1
index 9916178..0706b9a 100644
@@ -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
Signature · 1 line
2.9.3
Reviewed-by on v1 1/1
#1 lore raw
Quoted 13 lines · Daniel P. Berrange

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.

Quoted 4 lines
---
 .travis.yml | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)
#2 lore raw
In reply to Daniel P. Berrange
Quoted 31 lines · Daniel P. Berrange

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.

---
 .travis.yml | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)
.travis.yml +0 -1
index 9916178..0706b9a 100644
@@ -4,7 +4,6 @@ python:
   - "2.4"
 compiler:
   - gcc
-  - clang
 cache: ccache
 addons:
   apt:

.travis.yml script: · line 75

Quoted 9 lines
.travis.yml +3 -0
@@ -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