Commit c0ca86f510 for qemu.org

commit c0ca86f51037f99069bc08891efdc9ba8603539f
Author: Philippe Mathieu-Daudé <philmd@linaro.org>
Date:   Wed Mar 11 00:20:30 2026 +0100

    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>

diff --git a/tests/tcg/multiarch/Makefile.target b/tests/tcg/multiarch/Makefile.target
index 73c2a78215..1b5760c2f3 100644
--- a/tests/tcg/multiarch/Makefile.target
+++ b/tests/tcg/multiarch/Makefile.target
@@ -117,12 +117,19 @@ run-gdbstub-registers: sha512
 		--bin $< --test $(MULTIARCH_SRC)/gdbstub/registers.py, \
 	checking register enumeration)

+# The prot-none test was skipped on gitlab due to missing gdb-multiarch,
+# however it seems to have bitrotten. Disable, it is tracked as
+# https://gitlab.com/qemu-project/qemu/-/issues/3329
 run-gdbstub-prot-none: prot-none
+ifneq ($(GITLAB_CI),)
+	$(call skip-test, $<, "Broken on GitLab")
+else
 	$(call run-test, $@, env PROT_NONE_PY=1 $(GDB_SCRIPT) \
 		--gdb $(GDB) \
 		--qemu $(QEMU) --qargs "$(QEMU_OPTS)" \
 		--bin $< --test $(MULTIARCH_SRC)/gdbstub/prot-none.py, \
 	accessing PROT_NONE memory)
+endif

 run-gdbstub-catch-syscalls: catch-syscalls
 	$(call run-test, $@, $(GDB_SCRIPT) \