From: Thomas Huth <thuth@redhat.com>
To: qemu-devel@nongnu.org, "Alex Bennée" <alex.bennee@linaro.org>
Cc: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Willian Rampazzo" <wrampazz@redhat.com>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>
Subject: [PATCH v2 4/5] travis.yml: (Re-)move the --enable-debug jobs
Date: Fri, 5 Feb 2021 10:18:56 +0100 [thread overview]
Message-ID: <20210205091857.845389-5-thuth@redhat.com> (raw)
In-Reply-To: <20210205091857.845389-1-thuth@redhat.com>
We already have similar jobs in the gitlab-CI ("build-some-softmmu" and
"build-user-plugins"), so let's switch one of them to use --enable-debug
instead of --enable-debug-tcg, then we can simply drop these jobs from
the Travis-CI.
Signed-off-by: Thomas Huth <thuth@redhat.com>
---
.gitlab-ci.yml | 2 +-
.travis.yml | 12 ------------
2 files changed, 1 insertion(+), 13 deletions(-)
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 94c22ced7b..5926ec02a7 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -404,7 +404,7 @@ build-some-softmmu:
<<: *native_build_job_definition
variables:
IMAGE: debian-all-test-cross
- CONFIGURE_ARGS: --disable-tools --enable-debug-tcg
+ CONFIGURE_ARGS: --disable-tools --enable-debug
TARGETS: xtensa-softmmu arm-softmmu aarch64-softmmu alpha-softmmu
MAKE_CHECK_ARGS: check-tcg
diff --git a/.travis.yml b/.travis.yml
index 7744ec3a2f..f0e2b1059c 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -118,18 +118,6 @@ after_script:
jobs:
include:
- # --enable-debug implies --enable-debug-tcg, also runs quite a bit slower
- - name: "GCC debug (main-softmmu)"
- env:
- - CONFIG="--enable-debug --target-list=${MAIN_SOFTMMU_TARGETS}"
- - CACHE_NAME="${TRAVIS_BRANCH}-linux-gcc-debug"
-
-
- # TCG debug can be run just on its own and is mostly agnostic to user/softmmu distinctions
- - name: "GCC debug (user)"
- env:
- - CONFIG="--enable-debug-tcg --disable-system"
- - CACHE_NAME="${TRAVIS_BRANCH}-linux-gcc-debug-tcg"
# Using newer GCC with sanitizers
--
2.27.0
next prev parent reply other threads:[~2021-02-05 9:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-05 9:18 [PATCH v2 0/5] Move remaining x86 Travis jobs to the gitlab-CI Thomas Huth
2021-02-05 9:18 ` [PATCH v2 1/5] travis.yml: Move gprof/gcov test across to gitlab Thomas Huth
2021-02-05 13:37 ` Wainer dos Santos Moschetta
2021-02-05 16:58 ` Alex Bennée
2021-02-05 9:18 ` [PATCH v2 2/5] travis.yml: Move the -fsanitize=undefined test to the gitlab-CI Thomas Huth
2021-02-05 16:59 ` Alex Bennée
2021-02-05 9:18 ` [PATCH v2 3/5] travis.yml: Move the --enable-modules " Thomas Huth
2021-02-05 17:02 ` Alex Bennée
2021-02-05 9:18 ` Thomas Huth [this message]
2021-02-05 13:36 ` [PATCH v2 4/5] travis.yml: (Re-)move the --enable-debug jobs Wainer dos Santos Moschetta
2021-02-05 17:03 ` Alex Bennée
2021-02-05 9:18 ` [PATCH v2 5/5] travis.yml: Move the -fsanitize=thread testing to the gitlab-CI Thomas Huth
2021-02-05 17:47 ` Alex Bennée
2021-02-09 20:37 ` [PATCH v2 0/5] Move remaining x86 Travis jobs " Alex Bennée
2021-02-10 5:44 ` Thomas Huth
2021-02-10 7:17 ` 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=20210205091857.845389-5-thuth@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=wainersm@redhat.com \
--cc=wrampazz@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).