[PATCH] gitlab-ci: Only use one process in Windows jobs for compilation

[PATCH] gitlab-ci: Only use one process in Windows jobs for compilation

[Thomas Huth]

The Windows jobs are currently aborting at weird places - and
there's the suspicion that it's due to memory constraints in
the Windows containers. Let's switch to single-threaded compilation
to decrease the pressure on the memory load, and to make the
jobs more deterministic for further investigations.

Signed-off-by: Thomas Huth <thuth@redhat.com>
---
 .gitlab-ci.d/windows.yml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/.gitlab-ci.d/windows.yml b/.gitlab-ci.d/windows.yml
index c4bde758be..da6013904a 100644
--- a/.gitlab-ci.d/windows.yml
+++ b/.gitlab-ci.d/windows.yml
@@ -61,7 +61,7 @@ msys2-64bit:
   - .\msys64\usr\bin\bash -lc './configure --target-list=x86_64-softmmu
       --enable-capstone --without-default-devices'
   - .\msys64\usr\bin\bash -lc "sed -i '/^ROMS=/d' build/config-host.mak"
-  - .\msys64\usr\bin\bash -lc 'make -j2'
+  - .\msys64\usr\bin\bash -lc 'make'
   - .\msys64\usr\bin\bash -lc 'make check'
 
 msys2-32bit:
@@ -94,5 +94,5 @@ msys2-32bit:
   - mkdir output
   - cd output
   - ..\msys64\usr\bin\bash -lc "../configure --target-list=ppc64-softmmu"
-  - ..\msys64\usr\bin\bash -lc 'make -j2'
+  - ..\msys64\usr\bin\bash -lc 'make'
   - ..\msys64\usr\bin\bash -lc 'make check'
-- 
2.31.1

Re: [PATCH] gitlab-ci: Only use one process in Windows jobs for compilation

[Bin Meng]

On Fri, Aug 26, 2022 at 3:33 AM Thomas Huth <thuth@redhat.com> wrote:
>
> The Windows jobs are currently aborting at weird places - and
> there's the suspicion that it's due to memory constraints in
> the Windows containers. Let's switch to single-threaded compilation
> to decrease the pressure on the memory load, and to make the
> jobs more deterministic for further investigations.
>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
>  .gitlab-ci.d/windows.yml | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>

Reviewed-by: Bin Meng <bmeng.cn@gmail.com>

Could it be possibly caused by the windows version of meson? I once
saw the same build failure [1] on one Windows host with 64GiB memory
so I think it is not due to memory constraints on the build host.

[1] https://gitlab.com/stsquad/qemu/-/jobs/2765579267