qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: qemu-devel@nongnu.org, "Alex Bennée" <alex.bennee@linaro.org>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: "Daniel P . Berrangé" <berrange@redhat.com>
Subject: [PATCH 0/5] tests: Update Fedora and Alpine containers via lcitool
Date: Sat,  1 Jun 2024 09:05:38 +0200	[thread overview]
Message-ID: <20240601070543.37786-1-thuth@redhat.com> (raw)

According to QEMU's support policy, Fedora 38 and Alpine 3.18 are not
supported anymore, so let's bump the containers to a newer version.

Both, Alpine 3.20 and Fedora 40 ship with Python 3.12 that breaks our
old version of Avocado since the "imp" module has been removed there.
To work around this problem, Fedora fortunately still ships a separate
"python3-zombi-imp" package that we can install. And with regards to
Alpine, we only upgrade to 3.19 that is still using Python 3.11.

Another problem are improvements in the undefined-behavior sanitizer
of the latest versions of Clang that we use in the "clang-system"
Fedora container: We now need to compile with -fno-sanitize=function
there until all spots in the source code have been fixed (and that
might take while since many of the issues are not trivial).

Thomas Huth (5):
  tests/lcitool: Delete obsolete centos-stream-8.yml file
  tests/lcitool: Bump to latest libvirt-ci and update Fedora and Alpine
    version
  .gitlab-ci.d/buildtest.yml: Use -fno-sanitize=function in the
    clang-system job
  tests/lcitool: Install mingw-w64-tools for the Windows cross-builds
  tests/docker/dockerfiles: Run lcitool-refresh to update Fedora and
    Alpine

 .gitlab-ci.d/buildtest.yml                         | 1 +
 tests/docker/dockerfiles/alpine.docker             | 4 ++--
 tests/docker/dockerfiles/fedora-win64-cross.docker | 6 ++++--
 tests/docker/dockerfiles/fedora.docker             | 5 +++--
 tests/lcitool/libvirt-ci                           | 2 +-
 tests/lcitool/projects/qemu-win-installer.yml      | 1 +
 tests/lcitool/projects/qemu.yml                    | 1 +
 tests/lcitool/refresh                              | 6 +++---
 tests/lcitool/targets/centos-stream-8.yml          | 3 ---
 9 files changed, 16 insertions(+), 13 deletions(-)
 delete mode 100644 tests/lcitool/targets/centos-stream-8.yml

-- 
2.45.1



             reply	other threads:[~2024-06-01  7:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-01  7:05 Thomas Huth [this message]
2024-06-01  7:05 ` [PATCH 1/5] tests/lcitool: Delete obsolete centos-stream-8.yml file Thomas Huth
2024-06-03  9:32   ` Daniel P. Berrangé
2024-06-01  7:05 ` [PATCH 2/5] tests/lcitool: Bump to latest libvirt-ci and update Fedora and Alpine version Thomas Huth
2024-06-03  9:32   ` Daniel P. Berrangé
2024-06-01  7:05 ` [PATCH 3/5] .gitlab-ci.d/buildtest.yml: Use -fno-sanitize=function in the clang-system job Thomas Huth
2024-06-03  9:34   ` Daniel P. Berrangé
2024-06-01  7:05 ` [PATCH 4/5] tests/lcitool: Install mingw-w64-tools for the Windows cross-builds Thomas Huth
2024-06-03  9:34   ` Daniel P. Berrangé
2024-06-03 11:20   ` Philippe Mathieu-Daudé
2024-06-01  7:05 ` [PATCH 5/5] tests/docker/dockerfiles: Run lcitool-refresh to update Fedora and Alpine Thomas Huth
2024-06-03  9:35   ` Daniel P. Berrangé

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=20240601070543.37786-1-thuth@redhat.com \
    --to=thuth@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=berrange@redhat.com \
    --cc=philmd@linaro.org \
    --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).