From: "Alex Bennée" <alex.bennee@linaro.org>
To: qemu-devel@nongnu.org
Cc: fam@euphon.net, berrange@redhat.com, f4bug@amsat.org,
aurelien@aurel32.net, pbonzini@redhat.com, stefanha@redhat.com,
crosa@redhat.com, "Alex Bennée" <alex.bennee@linaro.org>
Subject: [PATCH v1 0/4] testing/next hotfix (revert bios build, mingw)
Date: Tue, 11 Oct 2022 12:34:13 +0100 [thread overview]
Message-ID: <20221011113417.794841-1-alex.bennee@linaro.org> (raw)
Hi,
Consider this a hotfix testing/next series. I hadn't noticed the
update to build the BIOS's would trigger a lot of downloading for a
normal build. I've reverted one patch which stops that from happening
and we can revisit enabling this is a more sustainable way later.
Also we have updates for the win32/64 builds which didn't make the
last PR although they currently rely on a out-of-tree libvirt-ci
update.
I'm still without CI minutes so haven't been able to run this through
gitlab yet.
Please review (and push to CI) so I can spin a PR today.
Alex Bennée (4):
tests/docker: update fedora-win[32|64]-cross with lcitool
tests/docker: update test-mingw to run single build
Revert "configure: build ROMs with container-based cross compilers"
configure: expose the direct container command
configure | 33 ++-
tests/docker/dockerfiles/alpine.docker | 2 +-
tests/docker/dockerfiles/centos8.docker | 2 +-
.../dockerfiles/debian-amd64-cross.docker | 234 ++++++++---------
tests/docker/dockerfiles/debian-amd64.docker | 236 +++++++++---------
.../dockerfiles/debian-arm64-cross.docker | 232 ++++++++---------
.../dockerfiles/debian-armel-cross.docker | 230 ++++++++---------
.../dockerfiles/debian-armhf-cross.docker | 232 ++++++++---------
.../dockerfiles/debian-mips64el-cross.docker | 226 ++++++++---------
.../dockerfiles/debian-mipsel-cross.docker | 226 ++++++++---------
.../dockerfiles/debian-ppc64el-cross.docker | 230 ++++++++---------
.../dockerfiles/debian-s390x-cross.docker | 228 ++++++++---------
.../dockerfiles/fedora-win32-cross.docker | 139 ++++++++---
.../dockerfiles/fedora-win64-cross.docker | 138 +++++++---
tests/docker/dockerfiles/fedora.docker | 230 ++++++++---------
tests/docker/dockerfiles/opensuse-leap.docker | 2 +-
tests/docker/dockerfiles/ubuntu2004.docker | 234 ++++++++---------
tests/docker/test-mingw | 16 +-
tests/lcitool/libvirt-ci | 2 +-
tests/lcitool/refresh | 48 ++--
20 files changed, 1520 insertions(+), 1400 deletions(-)
--
2.34.1
next reply other threads:[~2022-10-11 12:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 11:34 Alex Bennée [this message]
2022-10-11 11:34 ` [PATCH v1 1/4] tests/docker: update fedora-win[32|64]-cross with lcitool Alex Bennée
2022-10-11 14:26 ` Stefan Hajnoczi
2022-10-11 16:53 ` Alex Bennée
2022-10-11 11:34 ` [PATCH v1 2/4] tests/docker: update test-mingw to run single build Alex Bennée
2022-10-11 11:34 ` [PATCH v1 3/4] Revert "configure: build ROMs with container-based cross compilers" Alex Bennée
2022-10-11 18:38 ` Daniel Henrique Barboza
2022-10-11 11:34 ` [PATCH v1 4/4] configure: expose the direct container command Alex Bennée
2022-10-11 18:58 ` [PATCH v1 0/4] testing/next hotfix (revert bios build, mingw) Stefan Hajnoczi
2022-10-11 19:29 ` 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=20221011113417.794841-1-alex.bennee@linaro.org \
--to=alex.bennee@linaro.org \
--cc=aurelien@aurel32.net \
--cc=berrange@redhat.com \
--cc=crosa@redhat.com \
--cc=f4bug@amsat.org \
--cc=fam@euphon.net \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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).