From: "Alex Bennée" <alex.bennee@linaro.org>
To: qemu-devel@nongnu.org
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: [Qemu-devel] [PATCH 3/3] .travis.yml: disable Sparse testing
Date: Wed, 8 Jun 2016 17:54:18 +0100 [thread overview]
Message-ID: <1465404858-2484-4-git-send-email-alex.bennee@linaro.org> (raw)
In-Reply-To: <1465404858-2484-1-git-send-email-alex.bennee@linaro.org>
From: Paolo Bonzini <pbonzini@redhat.com>
On travis-ci.org, all builds fail with
/usr/include/features.h:324:11: error: unable to open bits/predefs.h
With "make docker-travis@ubuntu", they fail with
/usr/include/features.h:374:13: error: unable to open sys/cdefs.h
With "make docker-travis@fedora", finally, they fail due to sparse
not being able to parse some #pragmas in glib headers. Just kill
the thing from the CI builds.
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
[AJB: tweak title for my OCD]
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
---
.travis.yml | 3 ---
1 file changed, 3 deletions(-)
diff --git a/.travis.yml b/.travis.yml
index cde7d1a..c13881e 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -64,9 +64,6 @@ script:
- make -j3 && ${TEST_CMD}
matrix:
include:
- # Sparse is GCC only
- - env: CONFIG="--enable-sparse"
- compiler: gcc
# gprof/gcov are GCC features
- env: CONFIG="--enable-gprof --enable-gcov --disable-pie"
compiler: gcc
--
2.7.4
prev parent reply other threads:[~2016-06-08 16:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-08 16:54 [Qemu-devel] [PATCH 0/3] Current travis queue Alex Bennée
2016-06-08 16:54 ` [Qemu-devel] [PATCH 1/3] .travis.yml: add libnfs-dev for NFS block driver Alex Bennée
2016-06-08 16:54 ` [Qemu-devel] [PATCH 2/3] .travis.yml: add trusty GCE target Alex Bennée
2016-06-08 16:54 ` 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=1465404858-2484-4-git-send-email-alex.bennee@linaro.org \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).