qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Thomas Huth" <thuth@redhat.com>,
	"Beraldo Leal" <bleal@redhat.com>,
	"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
	"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
	"Li-Wen Hsu" <lwhsu@freebsd.org>, "Ed Maste" <emaste@freebsd.org>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"Daniel P. Berrangé" <berrange@redhat.com>
Subject: [PATCH v2 0/3] ci: refresh packages/containers and misc changes
Date: Fri, 22 Jul 2022 14:04:28 +0100	[thread overview]
Message-ID: <20220722130431.2319019-1-berrange@redhat.com> (raw)

Mostly this is to get the latest libvirt-ci content pulled in,
but I throw two small fixes on top.

Changed in v2:

  - Reworded various bits of the commit message
    for first patch

Daniel P. Berrangé (3):
  tests: refresh to latest libvirt-ci module
  gitlab: show testlog.txt contents when cirrus/custom-runner jobs fail
  gitlab: drop 'containers-layer2' stage

 .gitlab-ci.d/cirrus/build.yml                 |  3 ++-
 .gitlab-ci.d/cirrus/freebsd-12.vars           |  3 +--
 .gitlab-ci.d/cirrus/freebsd-13.vars           |  3 +--
 .gitlab-ci.d/cirrus/macos-11.vars             |  4 ++--
 .gitlab-ci.d/container-cross.yml              | 24 +++++++++----------
 .../custom-runners/centos-stream-8-x86_64.yml |  2 ++
 .../custom-runners/ubuntu-20.04-aarch32.yml   |  2 ++
 .../custom-runners/ubuntu-20.04-aarch64.yml   | 12 ++++++++++
 .../custom-runners/ubuntu-20.04-s390x.yml     | 12 ++++++++++
 .gitlab-ci.d/stages.yml                       |  1 -
 tests/docker/dockerfiles/alpine.docker        |  4 +++-
 tests/docker/dockerfiles/centos8.docker       |  6 ++---
 tests/docker/dockerfiles/debian-amd64.docker  |  2 ++
 .../dockerfiles/debian-arm64-cross.docker     |  2 ++
 .../dockerfiles/debian-armel-cross.docker     |  2 ++
 .../dockerfiles/debian-armhf-cross.docker     |  2 ++
 .../dockerfiles/debian-mips64el-cross.docker  |  2 ++
 .../dockerfiles/debian-mipsel-cross.docker    |  2 ++
 .../dockerfiles/debian-ppc64el-cross.docker   |  2 ++
 .../dockerfiles/debian-s390x-cross.docker     |  2 ++
 tests/docker/dockerfiles/fedora.docker        |  3 ++-
 tests/docker/dockerfiles/opensuse-leap.docker |  7 +++---
 tests/docker/dockerfiles/ubuntu2004.docker    |  2 ++
 tests/lcitool/libvirt-ci                      |  2 +-
 tests/lcitool/projects/qemu.yml               |  6 +++--
 tests/lcitool/refresh                         |  4 ++--
 26 files changed, 83 insertions(+), 33 deletions(-)

-- 
2.36.1



             reply	other threads:[~2022-07-22 13:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-22 13:04 Daniel P. Berrangé [this message]
2022-07-22 13:04 ` [PATCH v2 1/3] tests: refresh to latest libvirt-ci module Daniel P. Berrangé
2022-07-22 13:04 ` [PATCH v2 2/3] gitlab: show testlog.txt contents when cirrus/custom-runner jobs fail Daniel P. Berrangé
2022-07-22 13:04 ` [PATCH v2 3/3] gitlab: drop 'containers-layer2' stage Daniel P. Berrangé
2022-07-23 16:22 ` [PATCH v2 0/3] ci: refresh packages/containers and misc changes 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=20220722130431.2319019-1-berrange@redhat.com \
    --to=berrange@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=bleal@redhat.com \
    --cc=emaste@freebsd.org \
    --cc=f4bug@amsat.org \
    --cc=lwhsu@freebsd.org \
    --cc=qemu-devel@nongnu.org \
    --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).