From: Thomas Huth <thuth@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Cleber Rosa" <crosa@redhat.com>
Subject: [PATCH 0/7] Gitlab CI improvements and fixes
Date: Mon, 25 May 2020 15:18:16 +0200 [thread overview]
Message-ID: <20200525131823.715-1-thuth@redhat.com> (raw)
Currently, almost all piplines of our Gitlab CI are broken, since there
has been a change in the default Debian-based container that causes the
QEMU build process to fail (aka. the "BITS_PER_LONG" macro problem).
We could likely either wait for the containers to get fixed, or we could
try to work-around that issue in the QEMU sources, but considering that
we test with Ubuntu (and thus Debian-based) containers in our Travis-CI
already, we should maybe do something different here and rather switch
our Gitlab-CI to some RPM-based distros instead, to get even more test
coverage. This is now done in the 5th patch. Along the way, there are
clean-ups and some minor improvements, and a fix to be able to build QEMU
with Clang again (last patch).
After applying this patch series, the Gitlab-CI shows "green" again:
https://gitlab.com/huth/qemu/pipelines/149326595
Alex Bennée (1):
linux-user: limit check to HOST_LONG_BITS < TARGET_ABI_BITS
Cleber Rosa (1):
GitLab CI: avoid calling before_scripts on unintended jobs
Philippe Mathieu-Daudé (1):
gitlab-ci: Remove flex/bison packages
Thomas Huth (4):
MAINTAINERS: Add Philippe, Alex and Wainer to the Gitlab-CI section
gitlab-ci: Move edk2 and opensbi YAML files to .gitlab-ci.d folder
gitlab-ci: Do not use the standard container images from gitlab
gitlab-ci: Determine the number of jobs dynamically
.gitlab-ci-edk2.yml => .gitlab-ci.d/edk2.yml | 0
.../opensbi.yml | 0
.gitlab-ci.yml | 67 +++++++++++++------
MAINTAINERS | 5 +-
linux-user/elfload.c | 2 +
5 files changed, 51 insertions(+), 23 deletions(-)
rename .gitlab-ci-edk2.yml => .gitlab-ci.d/edk2.yml (100%)
rename .gitlab-ci-opensbi.yml => .gitlab-ci.d/opensbi.yml (100%)
--
2.18.1
next reply other threads:[~2020-05-25 13:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-25 13:18 Thomas Huth [this message]
2020-05-25 13:18 ` [PATCH 1/7] MAINTAINERS: Add Philippe, Alex and Wainer to the Gitlab-CI section Thomas Huth
2020-05-25 13:18 ` [PATCH 2/7] gitlab-ci: Remove flex/bison packages Thomas Huth
2020-05-27 16:47 ` Alex Bennée
2020-05-25 13:18 ` [PATCH 3/7] GitLab CI: avoid calling before_scripts on unintended jobs Thomas Huth
2020-05-27 17:33 ` Alex Bennée
2020-05-25 13:18 ` [PATCH 4/7] gitlab-ci: Move edk2 and opensbi YAML files to .gitlab-ci.d folder Thomas Huth
2020-05-25 13:32 ` Philippe Mathieu-Daudé
2020-05-27 17:34 ` Alex Bennée
2020-05-25 13:18 ` [PATCH 5/7] gitlab-ci: Do not use the standard container images from gitlab Thomas Huth
2020-05-28 8:37 ` Alex Bennée
2020-05-25 13:18 ` [PATCH 6/7] gitlab-ci: Determine the number of jobs dynamically Thomas Huth
2020-05-28 8:41 ` Alex Bennée
2020-05-28 9:11 ` Thomas Huth
2020-05-25 13:18 ` [PATCH 7/7] linux-user: limit check to HOST_LONG_BITS < TARGET_ABI_BITS Thomas Huth
2020-05-27 14:44 ` Laurent Vivier
2020-05-27 14:51 ` Thomas Huth
2020-05-27 16:36 ` Alex Bennée
2020-05-28 6:45 ` Thomas Huth
2020-05-28 8:31 ` 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=20200525131823.715-1-thuth@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=crosa@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=wainersm@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.