qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: qemu-devel@nongnu.org
Cc: "Alex Bennée" <alex.bennee@linaro.org>
Subject: [PULL v2 00/18] testing updates for 10.2
Date: Mon, 17 Nov 2025 15:52:37 +0000	[thread overview]
Message-ID: <20251117155237.4124861-1-alex.bennee@linaro.org> (raw)

The following changes since commit e88510fcdc13380bd4895a17d6f8a0b3a3325b85:

  Merge tag 'pull-target-arm-20251114' of https://gitlab.com/pm215/qemu into staging (2025-11-14 17:59:05 +0100)

are available in the Git repository at:

  https://gitlab.com/stsquad/qemu.git tags/pull-10.2-maintainer-171125-2

for you to fetch changes up to 8bec7b9874235e60f14172618121c60fdbd39302:

  gitlab: add a weekly container building job (2025-11-17 15:51:00 +0000)

----------------------------------------------------------------
testing updates for 10.2

  - fix emsdk image for podman
  - update lcitool and clean-up ENV stanzas
  - include coreutils for io tests
  - move a number of assets due to linaro changes
  - add ppc64le custom runner
  - rationalise the gitlab custom runners with templates
  - clean-up the custom runner rules
  - add a scheduled container build

----------------------------------------------------------------
Alex Bennée (17):
      tests/docker: drop --link from COPYs in emsdk docker
      libvirt-ci: bump libvirt-ci to latest version
      tests/lcitool: update ENV stanzas outputted by refresh
      tests/docker: add coreutils to the package list
      tests: move test_xen assets to share.linaro.org
      tests: move test_virt assets to share.linaro.org
      tests: move test_netdev_ethtool to share.linaro.org
      tests: move test_kvm_xen to share.linaro.org
      tests: move test_kvm to share.linaro.org
      tests: move test_virt_gpu to share.linaro.org
      gitlab: add initial ppc64le custom-runner test
      gitlab: use template for ubuntu-24.04-s390x jobs
      gitlab: simplify the ubuntu-24.04-aarch64 rules
      gitlab: suppress custom runners being triggered by schedule
      gitlab: make custom runners need QEMU_CI to run
      gitlab: make the schedule rules a bit more general
      gitlab: add a weekly container building job

Pierrick Bouvier (1):
      docs/about/emulation: update assets for uftrace plugin documentation

 docs/about/emulation.rst                           |  20 +--
 docs/devel/testing/ci-jobs.rst.inc                 |   6 +
 .gitlab-ci.d/base.yml                              |   4 +-
 .gitlab-ci.d/cirrus/freebsd-14.vars                |   2 +-
 .gitlab-ci.d/cirrus/macos-14.vars                  |   2 +-
 .gitlab-ci.d/container-template.yml                |   5 +
 .gitlab-ci.d/containers.yml                        |  39 +++++
 .gitlab-ci.d/custom-runners.yml                    |   1 +
 .gitlab-ci.d/custom-runners/debian-13-ppc64le.yml  |  45 +++++
 .../custom-runners/ubuntu-24.04-aarch64.yml        |  49 ++----
 .gitlab-ci.d/custom-runners/ubuntu-24.04-s390x.yml | 189 ++++++++-------------
 scripts/ci/setup/debian/debian-13-ppc64le.yaml     |   1 +
 scripts/ci/setup/ubuntu/ubuntu-2404-aarch64.yaml   |   1 +
 scripts/ci/setup/ubuntu/ubuntu-2404-s390x.yaml     |   1 +
 tests/docker/Makefile.include                      |  11 ++
 tests/docker/dockerfiles/alpine.docker             |  11 +-
 tests/docker/dockerfiles/centos9.docker            |  11 +-
 tests/docker/dockerfiles/debian-amd64-cross.docker |  21 +--
 tests/docker/dockerfiles/debian-arm64-cross.docker |  21 +--
 tests/docker/dockerfiles/debian-armhf-cross.docker |  21 +--
 tests/docker/dockerfiles/debian-i686-cross.docker  |  21 +--
 .../dockerfiles/debian-mips64el-cross.docker       |  21 +--
 .../docker/dockerfiles/debian-mipsel-cross.docker  |  21 +--
 .../docker/dockerfiles/debian-ppc64el-cross.docker |  21 +--
 .../docker/dockerfiles/debian-riscv64-cross.docker |  24 ++-
 tests/docker/dockerfiles/debian-s390x-cross.docker |  21 +--
 tests/docker/dockerfiles/debian.docker             |  13 +-
 tests/docker/dockerfiles/emsdk-wasm32-cross.docker |   8 +-
 .../docker/dockerfiles/fedora-rust-nightly.docker  |  11 +-
 tests/docker/dockerfiles/fedora-win64-cross.docker |  19 ++-
 tests/docker/dockerfiles/fedora.docker             |  11 +-
 tests/docker/dockerfiles/opensuse-leap.docker      |  11 +-
 tests/docker/dockerfiles/ubuntu2204.docker         |  11 +-
 tests/functional/aarch64/test_kvm.py               |   4 +-
 tests/functional/aarch64/test_virt.py              |   5 +-
 tests/functional/aarch64/test_virt_gpu.py          |   8 +-
 tests/functional/aarch64/test_xen.py               |  12 +-
 tests/functional/x86_64/test_kvm_xen.py            |  17 +-
 tests/functional/x86_64/test_netdev_ethtool.py     |  14 +-
 tests/lcitool/libvirt-ci                           |   2 +-
 tests/lcitool/projects/qemu.yml                    |   1 +
 tests/lcitool/refresh                              |   6 +-
 tests/vm/generated/freebsd.json                    |   1 +
 43 files changed, 393 insertions(+), 351 deletions(-)
 create mode 100644 .gitlab-ci.d/custom-runners/debian-13-ppc64le.yml

-- 
2.47.3



             reply	other threads:[~2025-11-17 15:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-17 15:52 Alex Bennée [this message]
2025-11-18 10:07 ` [PULL v2 00/18] testing updates for 10.2 Richard Henderson

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=20251117155237.4124861-1-alex.bennee@linaro.org \
    --to=alex.bennee@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).