On 23.08.2021 02:40, osstest service owner wrote: > branch xen-4.12-testing > xenbranch xen-4.12-testing > job test-amd64-i386-xl-qemuu-ovmf-amd64 > testid debian-hvm-install > > Tree: linux git://xenbits.xen.org/linux-pvops.git > Tree: linuxfirmware git://xenbits.xen.org/osstest/linux-firmware.git > Tree: ovmf git://xenbits.xen.org/osstest/ovmf.git > Tree: qemu git://xenbits.xen.org/qemu-xen-traditional.git > Tree: qemuu git://xenbits.xen.org/qemu-xen.git > Tree: seabios git://xenbits.xen.org/osstest/seabios.git > Tree: xen git://xenbits.xen.org/xen.git > > *** Found and reproduced problem changeset *** > > Bug is in tree: ovmf git://xenbits.xen.org/osstest/ovmf.git > Bug introduced: d06eb2d1d9dd8da1ed84bd08c5783a0264fe2b64 > Bug not present: 3357ac73807d83eb212632ee7c2e032a20a49c56 > Last fail repro: http://logs.test-lab.xenproject.org/osstest/logs/164383/ > > > commit d06eb2d1d9dd8da1ed84bd08c5783a0264fe2b64 > Author: Laszlo Ersek <[email protected]> > Date: Wed May 26 22:14:24 2021 +0200 > > OvmfPkg/PlatformPei: remove Xen support
Uniformly from 4.15 through to 4.12 (the latter of which shouldn't have been affected by whatever has been pulled in in the first place, given it's a security-only branch, but with the OVMF commit to use being hardcoded in ./Config.mk I don't really understand how a possible change to the OVMF tree could have affected this version) tests are now failing, everywhere with the above bisection result. Given that we want to get out releases from the 4.15 and 4.13 branches right after the batch of XSAs going public on Wednesday, something needs to be done about this pretty soon. Does osstest override ./Config.mk's choice? Albeit I guess even if it does that's not outright wrong, and instead it would be bad if the older versions wouldn't work anymore with an updated OVMF. Thank you for looking into this, Jan
