On Thu, 9 Mar 2023 at 11:58, Gerd Hoffmann <kra...@redhat.com> wrote: > > The following changes since commit 9832009d9dd2386664c15cc70f6e6bfe062be8bd: > > Merge tag 'pull-riscv-to-apply-20230306' of > https://gitlab.com/palmer-dabbelt/qemu into staging (2023-03-07 12:53:00 > +0000) > > are available in the Git repository at: > > https://gitlab.com/kraxel/qemu.git > tags/edk2-stable202302-20230309-pull-request > > for you to fetch changes up to 75bc97ac50634229fa9da45faa1fa64bbe6024c7: > > edk2: update firmware binaries (2023-03-09 12:49:29 +0100) > > ---------------------------------------------------------------- > edk2: update to 202302 stable tag > > ---------------------------------------------------------------- > > Gerd Hoffmann (3): > edk2: update submodule to edk2-stable202302 > edk2: replace build scripts > edk2: update firmware binaries
The docker-edk2 CI job fails: https://gitlab.com/qemu-project/qemu/-/jobs/3910666498 Step 1/3 : FROM ubuntu:18.04 18.04: Pulling from library/ubuntu mediaType in manifest should be 'application/vnd.docker.distribution.manifest.v2+json' not 'application/vnd.oci.image.manifest.v1+json' This may be fixable with an equivalent of: https://lore.kernel.org/qemu-devel/20230224212543.20462-2-pal...@rivosinc.com/ for .gitlab-ci.d/edk2.yml What I still do not understand is why we have both: (1) binaries of edk2 committed to git (2) a gitlab CI job that is building edk2 The bios-tables-test also fails: https://gitlab.com/qemu-project/qemu/-/jobs/3910666555 (but also seen on other configs): ▶ 206/206 ERROR:../tests/qtest/acpi-utils.c:158:acpi_find_rsdp_address_uefi: code should not be reached ERROR 206/206 qemu:qtest+qtest-aarch64 / qtest-aarch64/bios-tables-test ERROR 706.75s killed by signal 6 SIGABRT (I also tested this with the qga and hexagon pullreqs, but neither of those should have affected this.) thanks -- PMM
