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: "John Snow" <jsnow@redhat.com>, "Thomas Huth" <thuth@redhat.com>,
	"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
	"Marc-André Lureau" <marcandre.lureau@redhat.com>,
	"Markus Armbruster" <armbru@redhat.com>,
	"Daniel P. Berrangé" <berrange@redhat.com>,
	"Stefan Hajnoczi" <stefanha@redhat.com>,
	"Bastian Koppelmann" <kbastian@mail.uni-paderborn.de>,
	"Cleber Rosa" <crosa@redhat.com>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: [PATCH 0/5] testing/next: docker, ansible
Date: Tue,  7 Mar 2023 14:38:14 +0000	[thread overview]
Message-ID: <20230307143819.510186-1-alex.bennee@linaro.org> (raw)

A quick fix to docker which should help layer re-use. I was also
trying to get the KVM version of the boot_linux.py tests running on
the centos8-stream machine so we could disable the TCG equivalents.
Unfortunately this doesn't help as the TCG versions exercise both the
fdc emulation and the out-of-kernel APIC emulation. We may not care
too much about the fdc coverage but it would be awesome if we could
find a better way of exercising the x86 interrupt controller code than
running a very slow distro boot.

Alex Bennée (4):
  tests/docker: all add DOCKER_BUILDKIT to RUNC environment
  scripts/ci: add libslirp-devel to build-environment
  scripts/ci: update gitlab-runner playbook to handle CentOS
  gitlab: update centos-8-stream job

Marcin Juszkiewicz (1):
  tests/avocado: update AArch64 tests to Alpine 3.17.2

 .../custom-runners/centos-stream-8-x86_64.yml | 18 ++++++-----------
 .../org.centos/stream/8/build-environment.yml |  1 +
 scripts/ci/setup/gitlab-runner.yml            | 20 +++++++++++++++++--
 tests/avocado/machine_aarch64_virt.py         |  8 ++++----
 tests/docker/Makefile.include                 |  2 +-
 5 files changed, 30 insertions(+), 19 deletions(-)

-- 
2.39.2



             reply	other threads:[~2023-03-07 14:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-07 14:38 Alex Bennée [this message]
2023-03-07 14:38 ` [PATCH 1/5] tests/avocado: update AArch64 tests to Alpine 3.17.2 Alex Bennée
2023-03-07 15:03   ` Philippe Mathieu-Daudé
2023-03-07 14:38 ` [PATCH 2/5] tests/docker: all add DOCKER_BUILDKIT to RUNC environment Alex Bennée
2023-03-07 14:38 ` [PATCH 3/5] scripts/ci: add libslirp-devel to build-environment Alex Bennée
2023-03-07 14:42   ` Thomas Huth
2023-03-07 14:38 ` [PATCH 4/5] scripts/ci: update gitlab-runner playbook to handle CentOS Alex Bennée
2023-03-07 14:38 ` [PATCH 5/5] gitlab: update centos-8-stream job 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=20230307143819.510186-1-alex.bennee@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=crosa@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=kbastian@mail.uni-paderborn.de \
    --cc=marcandre.lureau@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=thuth@redhat.com \
    --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 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).