All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] travis: disable Sparse testing
Date: Mon, 06 Jun 2016 16:24:12 +0100	[thread overview]
Message-ID: <877fe2ibmr.fsf@linaro.org> (raw)
In-Reply-To: <1465223987-135491-1-git-send-email-pbonzini@redhat.com>


Paolo Bonzini <pbonzini@redhat.com> writes:

> On travis-ci.org, all builds fail with
>    /usr/include/features.h:324:11: error: unable to open
>    bits/predefs.h

Hmm when did this start failing?

Interesting the build still manages to struggle through:

  https://travis-ci.org/qemu/qemu/jobs/135572286

>
> 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>
> ---
>  .travis.yml | 3 ---
>  1 file changed, 3 deletions(-)
>
> diff --git a/.travis.yml b/.travis.yml
> index 50ac17f..425cbe1 100644
> --- a/.travis.yml
> +++ b/.travis.yml
> @@ -63,9 +63,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


--
Alex Bennée

  reply	other threads:[~2016-06-06 15:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-06 14:39 [Qemu-devel] [PATCH] travis: disable Sparse testing Paolo Bonzini
2016-06-06 15:24 ` Alex Bennée [this message]
2016-06-06 15:31   ` Paolo Bonzini
2016-06-06 16:17   ` Peter Maydell
2016-06-06 17:29     ` Alex Bennée

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=877fe2ibmr.fsf@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 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.