| Message ID | 20240206124947.1617078-3-romain.naour@smile.fr |
|---|---|
| State | Accepted |
| Headers | show |
| Series | TestGlxinfo fixes | expand |
diff --git a/support/testing/tests/package/test_glxinfo.py b/support/testing/tests/package/test_glxinfo.py index 6bedee5298..3ccbdca8d9 100644 --- a/support/testing/tests/package/test_glxinfo.py +++ b/support/testing/tests/package/test_glxinfo.py @@ -42,7 +42,8 @@ class TestGlxinfo(infra.basetest.BRTest): self.emulator.boot(arch="i386", kernel=kern, kernel_cmdline=["root=/dev/vda console=ttyS0"], - options=["-M", "pc", "-m", "512", "-drive", "file={},if=virtio,format=raw".format(img)]) + options=["-M", "pc", "-cpu", "core2duo", "-m", "512", + "-drive", "file={},if=virtio,format=raw".format(img)]) self.emulator.login() def test_run(self):
TestGlxinfo fail with a new runtime error: # glxinfo -B -display :0 name of display: :0 traps: glxinfo[84] trap invalid opcode ip:b73c7027 sp:bf8433c0 error:0 in swrast_dri.so[b6e4c000+64f000] Illegal instruction The x86-core2 Bootlin toolchains are built for a core2 CPU [0], this means that the Bootlin toolchains may use core2-specific instructions. The TestGlxinfo test is setup for BR2_x86_core2, so our executables will also contain core2 instructions. However, the default Qemu x86 is not guaranteed to emulate all the instructions specific to core2, causing runtime issues as reported above. A similar issue has been fixed by adding Nehalem cpu emulation on the qemu command line. See 4f565b5222 ("support/testing: use Nehalem cpu emulation for TestGrubX8664EFI"). Set core2duo cpu emulation for TestGlxinfo on the qemu command line. [0] https://gitlab.com/buildroot.org/toolchains-builder/-/blob/kubu/toolchain-builder-2023.08/configs/arch/x86-core2.config?ref_type=heads Signed-off-by: Romain Naour <romain.naour@smile.fr> --- support/testing/tests/package/test_glxinfo.py | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)