From: Thomas Huth <thuth@redhat.com>
To: qemu-devel@nongnu.org, Peter Maydell <peter.maydell@linaro.org>
Cc: "Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: [PULL 12/13] gitlab-ci: Move coroutine tests across to gitlab
Date: Wed, 9 Dec 2020 10:48:55 +0100 [thread overview]
Message-ID: <20201209094856.17788-13-thuth@redhat.com> (raw)
In-Reply-To: <20201209094856.17788-1-thuth@redhat.com>
From: Philippe Mathieu-Daudé <philmd@redhat.com>
Similarly to commit 8cdb2cef3f1, move the coroutine tests to GitLab.
Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Message-Id: <20201108204535.2319870-13-philmd@redhat.com>
Reviewed-by: Wainer dos Santos Moschetta <wainersm@redhat.com>
[thuth: Replaced Travis by Gitlab-CI in comment]
Signed-off-by: Thomas Huth <thuth@redhat.com>
---
.gitlab-ci.yml | 16 ++++++++++++++++
.travis.yml | 14 --------------
2 files changed, 16 insertions(+), 14 deletions(-)
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 7381c7858d..873ed19fcf 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -413,6 +413,22 @@ build-tci:
- QTEST_QEMU_BINARY="./qemu-system-x86_64" ./tests/qtest/pxe-test
- QTEST_QEMU_BINARY="./qemu-system-s390x" ./tests/qtest/pxe-test -m slow
+# Alternate coroutines implementations are only really of interest to KVM users
+# However we can't test against KVM on Gitlab-CI so we can only run unit tests
+build-coroutine-ucontext:
+ <<: *native_build_job_definition
+ variables:
+ IMAGE: ubuntu2004
+ CONFIGURE_ARGS: --with-coroutine=ucontext --disable-tcg
+ MAKE_CHECK_ARGS: check-unit
+
+build-coroutine-sigaltstack:
+ <<: *native_build_job_definition
+ variables:
+ IMAGE: ubuntu2004
+ CONFIGURE_ARGS: --with-coroutine=sigaltstack --disable-tcg
+ MAKE_CHECK_ARGS: check-unit
+
# Most jobs test latest gcrypt or nettle builds
#
# These jobs test old gcrypt and nettle from RHEL7
diff --git a/.travis.yml b/.travis.yml
index 12828f351c..d01714a5ae 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -148,20 +148,6 @@ jobs:
- CACHE_NAME="${TRAVIS_BRANCH}-linux-gcc-default"
- # Alternate coroutines implementations are only really of interest to KVM users
- # However we can't test against KVM on Travis so we can only run unit tests
- - name: "check-unit coroutine=ucontext"
- env:
- - CONFIG="--with-coroutine=ucontext --disable-tcg"
- - TEST_CMD="make check-unit -j${JOBS} V=1"
-
-
- - name: "check-unit coroutine=sigaltstack"
- env:
- - CONFIG="--with-coroutine=sigaltstack --disable-tcg"
- - TEST_CMD="make check-unit -j${JOBS} V=1"
-
-
# Check we can build docs and tools (out of tree)
- name: "tools and docs (bionic)"
dist: bionic
--
2.18.4
next prev parent reply other threads:[~2020-12-09 9:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-09 9:48 [PULL 00/13] Gitlab-CI and test patches Thomas Huth
2020-12-09 9:48 ` [PULL 01/13] gitlab-ci: Document 'build-tcg-disabled' is a KVM X86 job Thomas Huth
2020-12-09 9:48 ` [PULL 02/13] gitlab-ci: Replace YAML anchors by extends (cross_system_build_job) Thomas Huth
2020-12-09 9:48 ` [PULL 03/13] gitlab-ci: Introduce 'cross_accel_build_job' template Thomas Huth
2020-12-09 9:48 ` [PULL 04/13] gitlab-ci: Add KVM s390x cross-build jobs Thomas Huth
2020-12-09 9:48 ` [PULL 05/13] gitlab-ci: Add Xen " Thomas Huth
2020-12-09 9:48 ` [PULL 06/13] test-qga: fix a resource leak in test_qga_guest_get_osinfo() Thomas Huth
2020-12-09 9:48 ` [PULL 07/13] tests/qtest/fuzz-test: Quit test_lp1878642 once done Thomas Huth
2020-12-09 9:48 ` [PULL 08/13] fuzz: avoid double-fetches by default Thomas Huth
2020-12-09 9:48 ` [PULL 09/13] gitlab-ci: Split CONFIGURE_ARGS one argument per line for build-disabled Thomas Huth
2020-12-09 9:48 ` [PULL 10/13] gitlab-ci: Update 'build-disabled' to cover all configurable options Thomas Huth
2020-12-09 9:48 ` [PULL 11/13] gitlab-ci: Move user-static test across to gitlab Thomas Huth
2020-12-09 9:48 ` Thomas Huth [this message]
2020-12-09 9:48 ` [PULL 13/13] hw/m68k/mcf5206: Don't leak IRQs in mcf5206_mbar_realize() Thomas Huth
2020-12-09 20:08 ` [PULL 00/13] Gitlab-CI and test patches Peter Maydell
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=20201209094856.17788-13-thuth@redhat.com \
--to=thuth@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@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).