All of lore.kernel.org
 help / color / mirror / Atom feed
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 0/5] Move remaining x86 Travis jobs to the gitlab-CI
Date: Fri,  5 Feb 2021 10:18:52 +0100	[thread overview]
Message-ID: <20210205091857.845389-1-thuth@redhat.com> (raw)

Since Travis changed their policies, travis-ci.org will soon become
completely useless for the QEMU project. We should now really make sure
that we move the remaining tests as good as possible to the gitlab-CI
instead.

v2:
 - Run "make check" in the gprof/gcov test
 - Make sure that we run at least one test with --enable-debug
 - Reworked the thread sanitizer patch to use --enable-tsan + clang now

Philippe Mathieu-Daudé (1):
  travis.yml: Move gprof/gcov test across to gitlab

Thomas Huth (4):
  travis.yml: Move the -fsanitize=undefined test to the gitlab-CI
  travis.yml: Move the --enable-modules test to the gitlab-CI
  travis.yml: (Re-)move the --enable-debug jobs
  travis.yml: Move the -fsanitize=thread testing to the gitlab-CI

 .gitlab-ci.yml                             |  38 ++++++-
 .travis.yml                                | 111 ---------------------
 MAINTAINERS                                |   2 +-
 scripts/{travis => ci}/coverage-summary.sh |   2 +-
 tests/docker/dockerfiles/ubuntu2004.docker |   2 +
 5 files changed, 39 insertions(+), 116 deletions(-)
 rename scripts/{travis => ci}/coverage-summary.sh (92%)

-- 
2.27.0



             reply	other threads:[~2021-02-05  9:21 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-05  9:18 Thomas Huth [this message]
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 ` [PATCH v2 4/5] travis.yml: (Re-)move the --enable-debug jobs Thomas Huth
2021-02-05 13:36   ` 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-1-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 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.