From: "Alex Bennée" <alex.bennee@linaro.org>
To: famz@redhat.com, pbonzini@redhat.com, stefanha@redhat.com,
stefanb@linux.vnet.ibm.com, marcandre.lureau@redhat.com
Cc: qemu-devel@nongnu.org, "Alex Bennée" <alex.bennee@linaro.org>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>
Subject: [Qemu-devel] [RFC PATCH 1/2] .travis.yml: disable linux-user build for gcov
Date: Fri, 18 May 2018 10:14:39 +0100 [thread overview]
Message-ID: <20180518091440.1559-2-alex.bennee@linaro.org> (raw)
In-Reply-To: <20180518091440.1559-1-alex.bennee@linaro.org>
Currently the default testing doesn't exercise the linux-user builds
so there is no point spending time building them. We may want to
enable a separate gcov build once linux-user testing is re-enabled
although it's likely to report very low coverage.
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
---
.travis.yml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/.travis.yml b/.travis.yml
index c1e99237b2..aa83e9aed7 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -74,7 +74,7 @@ matrix:
- env: CONFIG=""
compiler: clang
# gprof/gcov are GCC features
- - env: CONFIG="--enable-gprof --enable-gcov --disable-pie"
+ - env: CONFIG="--enable-gprof --enable-gcov --disable-pie --disable-linux-user"
compiler: gcc
# We manually include builds which we disable "make check" for
- env: CONFIG="--enable-debug --enable-tcg-interpreter"
--
2.17.0
next prev parent reply other threads:[~2018-05-18 9:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-18 9:14 [Qemu-devel] [RFC PATCH 0/2] Travis Stability Patches Alex Bennée
2018-05-18 9:14 ` Alex Bennée [this message]
2018-05-18 9:14 ` [Qemu-devel] [RFC PATCH 2/2] tests/Makefile: comment out flakey tests Alex Bennée
2018-05-18 9:49 ` Paolo Bonzini
2018-05-18 10:02 ` Peter Maydell
2018-05-18 10:17 ` Peter Maydell
2018-05-18 12:02 ` Stefan Hajnoczi
2018-05-18 15:08 ` Alex Bennée
2018-05-25 9:17 ` Stefan Hajnoczi
2018-05-18 18:31 ` Peter Maydell
2018-05-19 6:10 ` Thomas Huth
2018-05-19 11:36 ` Peter Maydell
2018-05-22 6:01 ` Thomas Huth
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=20180518091440.1559-2-alex.bennee@linaro.org \
--to=alex.bennee@linaro.org \
--cc=f4bug@amsat.org \
--cc=famz@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanb@linux.vnet.ibm.com \
--cc=stefanha@redhat.com \
/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).