On 13/6/22 19:12, Alex Bennée wrote:
Running on all 80 cores of our aarch64 runner does occasionally
trigger a race condition which fails the build. However the CI system
is not the time and place to play with much heisenbugs so turn down
the nproc to "only" use 40 cores in the build.
Signed-off-by: Alex Bennée <alex.ben...@linaro.org>
---
.../custom-runners/ubuntu-20.04-aarch32.yml | 4 ++--
.../custom-runners/ubuntu-20.04-aarch64.yml | 24 +++++++++----------
2 files changed, 14 insertions(+), 14 deletions(-)
diff --git a/.gitlab-ci.d/custom-runners/ubuntu-20.04-aarch32.yml
b/.gitlab-ci.d/custom-runners/ubuntu-20.04-aarch32.yml
index 47856ac53c..1998460d06 100644
--- a/.gitlab-ci.d/custom-runners/ubuntu-20.04-aarch32.yml
+++ b/.gitlab-ci.d/custom-runners/ubuntu-20.04-aarch32.yml
@@ -19,5 +19,5 @@ ubuntu-20.04-aarch32-all:
- mkdir build
- cd build
- ../configure --cross-prefix=arm-linux-gnueabihf-
- - make --output-sync -j`nproc`
- - make --output-sync -j`nproc` check V=1
+ - make --output-sync -j`nproc --ignore=40`
+ - make --output-sync -j`nproc --ignore=40` check V=1
Alternatively:
-j$(expr $(nproc) / 2)
So we don't have to update the configs if the runner gets its hardware
updated.
Reviewed-by: Philippe Mathieu-Daudé <f4...@amsat.org>
