reproducing in a porterbox ... with qemu 1:10.0.2+ds-1ubuntu2
$ PYTHONPATH=./debian/python python3 debian/tests/shell.py ... Ran 25 tests in 16.891s with qemu 1:10.1.0~rc2+ds-1ubuntu1 $ PYTHONPATH=./debian/python python3 debian/tests/shell.py ... (hangs as in the autopkgtest) (remember this only fails on armhf, all other host platforms work fine) Isolating the failing commands like /usr/bin/qemu-system-i386 -machine q35,accel=tcg -no-user-config -nodefaults -m 256 -smp 1,sockets=1,cores=1,threads=1 -display none -serial stdio -chardev pty,id=charserial1 -device isa- serial,chardev=charserial1,id=serial1 -drive file=/usr/share/OVMF/OVMF32_CODE_4M.fd,if=pflash,format=raw,unit=0,readonly=on -drive file=/tmp/tmp0b6qq28g,if=pflash,format=raw,unit=1,readonly=off Only difference is the machine type q35 vs pc and different tmp files to boot into. By the above we know it is excuting/emulating i386 code in all cases. Not sure if needed, but saving one of these tmp files to recreate it without the wrapper ... The q35 case seems to be a bit more intense to the system grinding much to a halt. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2121495 Title: edk2 test on armhf breaks with qemu 10.1 in questing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/2121495/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
