@samitouri / QOSamiQemu / commits / c0ca86f510

tests/tcg: Disable prot-none test on GitLab

When adding gdb-multiarch on our container images, we see the prot-none tests to pass on GitHub but fail on GitLab. Disable and track: https://gitlab.com/qemu-project/qemu/-/issues/3329 Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org> Reviewed-by: Pierrick Bouvier <pierrick.bouvier@linaro.org> Link: https://lore.kernel.org/qemu-devel/20260310232045.58440-3-philmd@linaro.org Signed-off-by: Pierrick Bouvier <pierrick.bouvier@linaro.org>

Philippe Mathieu-Daudé committed Mar 11, 2026 at 00:20 UTC c0ca86f51037f99069bc08891efdc9ba8603539f
1 file changed +7
tests/tcg/multiarch/Makefile.target
+7
@@ -117,12 +117,19 @@ run-gdbstub-registers: sha512
117 --bin $< --test $(MULTIARCH_SRC)/gdbstub/registers.py, \
118 checking register enumeration)
119
120 +# The prot-none test was skipped on gitlab due to missing gdb-multiarch,
121 +# however it seems to have bitrotten. Disable, it is tracked as
122 +# https://gitlab.com/qemu-project/qemu/-/issues/3329
123 run-gdbstub-prot-none: prot-none
124 +ifneq ($(GITLAB_CI),)
125 + $(call skip-test, $<, "Broken on GitLab")
126 +else
127 $(call run-test, $@, env PROT_NONE_PY=1 $(GDB_SCRIPT) \
128 --gdb $(GDB) \
129 --qemu $(QEMU) --qargs "$(QEMU_OPTS)" \
130 --bin $< --test $(MULTIARCH_SRC)/gdbstub/prot-none.py, \
131 accessing PROT_NONE memory)
132 +endif
133
134 run-gdbstub-catch-syscalls: catch-syscalls
135 $(call run-test, $@, $(GDB_SCRIPT) \