The gdb jobs fail on CI and although I can't replicate locally on the
machine I have access to it definitely fixes it for the gitlab CI
machines.

Signed-off-by: Alex Bennée <alex.bennee@linaro.org>

---
v2
  - better commit message.
---
 .gitlab-ci.d/macos.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.gitlab-ci.d/macos.yml b/.gitlab-ci.d/macos.yml
index 53b6e6c4d8f..641a48b3832 100644
--- a/.gitlab-ci.d/macos.yml
+++ b/.gitlab-ci.d/macos.yml
@@ -22,7 +22,7 @@
     - export PKG_CONFIG_PATH="$PKG_CONFIG_PATH"
     - brew update
     - brew install $PKGS
-    - brew install gdb aarch64-elf-gcc i686-elf-gcc x86_64-elf-gcc
+    - brew install aarch64-elf-gcc i686-elf-gcc x86_64-elf-gcc
     - if test -n "$PYPI_PKGS" ; then PYLIB=$($PYTHON -c 'import sysconfig; print(sysconfig.get_path("stdlib"))'); rm -f $PYLIB/EXTERNALLY-MANAGED; $PIP3 install --break-system-packages $PYPI_PKGS ; fi
   script:
     - mkdir build
-- 
2.47.3

On Mon, Jul 20, 2026 at 2:09 PM Alex Bennée <alex.bennee@linaro.org> wrote:
>
> The gdb jobs fail on CI and although I can't replicate locally on the
> machine I have access to it definitely fixes it for the gitlab CI
> machines.
>
> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>

Merged, thanks!

Stefan

Hi Alex,

On 20/7/26 20:04, Alex Bennée wrote:
> The gdb jobs fail on CI

What is the CI failure? Could we at least record where the
CI console fail?

I'm worried to recall what was the issue when trying to fix
this in the future.

> and although I can't replicate locally on the
> machine I have access to it definitely fixes it for the gitlab CI
> machines.
> 
> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
> 
> ---
> v2
>    - better commit message.
> ---
>   .gitlab-ci.d/macos.yml | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/.gitlab-ci.d/macos.yml b/.gitlab-ci.d/macos.yml
> index 53b6e6c4d8f..641a48b3832 100644
> --- a/.gitlab-ci.d/macos.yml
> +++ b/.gitlab-ci.d/macos.yml
> @@ -22,7 +22,7 @@
>       - export PKG_CONFIG_PATH="$PKG_CONFIG_PATH"
>       - brew update
>       - brew install $PKGS
> -    - brew install gdb aarch64-elf-gcc i686-elf-gcc x86_64-elf-gcc
> +    - brew install aarch64-elf-gcc i686-elf-gcc x86_64-elf-gcc

Maybe add a comment "# we ought to install gdb but ..."

>       - if test -n "$PYPI_PKGS" ; then PYLIB=$($PYTHON -c 'import sysconfig; print(sysconfig.get_path("stdlib"))'); rm -f $PYLIB/EXTERNALLY-MANAGED; $PIP3 install --break-system-packages $PYPI_PKGS ; fi
>     script:
>       - mkdir build

On Mon, Jul 20, 2026 at 4:28 PM Philippe Mathieu-Daudé
<philmd@oss.qualcomm.com> wrote:
> On 20/7/26 20:04, Alex Bennée wrote:
> > The gdb jobs fail on CI
>
> What is the CI failure? Could we at least record where the
> CI console fail?
>
> I'm worried to recall what was the issue when trying to fix
> this in the future.

I added the following to the commit message when merging this for -rc1:

  This fixes the following CI jobs: aarch64-macos-15-build and
  aarch64-macos-26-build.

  Removing gdb from macOS jobs skips the softmmu gdbstub tests which
  currently hang on GitLab's macOS runners:

  qemu-system-aarch64: -gdb
unix:path=/var/folders/fc/8_hzw5tx3n7c9c04tzd6tv_40000gn/T/tmpes3paikrqemu-gdbstub/gdbstub.socket,server=on:
info: QEMU waiting for connection on:
disconnected:unix:/var/folders/fc/8_hzw5tx3n7c9c04tzd6tv_40000gn/T/tmpes3paikrqemu-gdbstub/gdbstub.socket,server=on
  gmake[1]: ***
[/Users/gitlab/builds/qemu-project/qemu/tests/tcg/multiarch/system/Makefile.softmmu-target:35:
run-gdbstub-interrupt] Error 137
  gmake: *** [/Users/gitlab/builds/qemu-project/qemu/tests/Makefile.include:75:
run-tcg-tests-aarch64-softmmu] Error 2

  The following GitLab work item tracks solving the underlying issue that
  is hanging softmmu gdbstub tests:
  https://gitlab.com/qemu-project/qemu/-/work_items/4063

Stefan

On 21/7/26 16:15, Stefan Hajnoczi wrote:
> On Mon, Jul 20, 2026 at 4:28 PM Philippe Mathieu-Daudé
> <philmd@oss.qualcomm.com> wrote:
>> On 20/7/26 20:04, Alex Bennée wrote:
>>> The gdb jobs fail on CI
>>
>> What is the CI failure? Could we at least record where the
>> CI console fail?
>>
>> I'm worried to recall what was the issue when trying to fix
>> this in the future.
> 
> I added the following to the commit message when merging this for -rc1:
> 
>    This fixes the following CI jobs: aarch64-macos-15-build and
>    aarch64-macos-26-build.
> 
>    Removing gdb from macOS jobs skips the softmmu gdbstub tests which
>    currently hang on GitLab's macOS runners:
> 
>    qemu-system-aarch64: -gdb
> unix:path=/var/folders/fc/8_hzw5tx3n7c9c04tzd6tv_40000gn/T/tmpes3paikrqemu-gdbstub/gdbstub.socket,server=on:
> info: QEMU waiting for connection on:
> disconnected:unix:/var/folders/fc/8_hzw5tx3n7c9c04tzd6tv_40000gn/T/tmpes3paikrqemu-gdbstub/gdbstub.socket,server=on
>    gmake[1]: ***
> [/Users/gitlab/builds/qemu-project/qemu/tests/tcg/multiarch/system/Makefile.softmmu-target:35:
> run-gdbstub-interrupt] Error 137
>    gmake: *** [/Users/gitlab/builds/qemu-project/qemu/tests/Makefile.include:75:
> run-tcg-tests-aarch64-softmmu] Error 2
> 
>    The following GitLab work item tracks solving the underlying issue that
>    is hanging softmmu gdbstub tests:
>    https://gitlab.com/qemu-project/qemu/-/work_items/4063

Thank you Stefan! :)

On 7/20/2026 11:04 AM, Alex Bennée wrote:
> The gdb jobs fail on CI and although I can't replicate locally on the
> machine I have access to it definitely fixes it for the gitlab CI
> machines.
> 
> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
> 
> ---
> v2
>   - better commit message.
> ---
>  .gitlab-ci.d/macos.yml | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 

Reviewed-by: Pierrick Bouvier <pierrick.bouvier@oss.qualcomm.com>