From fd8b0a44c4768be62d162fee0a681ab9a8be7970 Mon Sep 17 00:00:00 2001 From: Ebrahim Byagowi Date: Mon, 29 Jun 2020 00:19:38 +0430 Subject: [PATCH] [ci] Limit number of processes ninja uses Our CricleCI bots run with 32 cores last time I check which makes random compile issues like this https://circleci.com/gh/harfbuzz/harfbuzz/146030 to happen. Guess that has something to do with the way virtualization is done in Circle CI so let's limit number of processes. --- .circleci/config.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.circleci/config.yml b/.circleci/config.yml index 95dab4171..a4231938d 100644 --- a/.circleci/config.yml +++ b/.circleci/config.yml @@ -222,11 +222,11 @@ jobs: - run: pip3 install fonttools --upgrade - run: pip3 install git+https://github.com/mesonbuild/meson # use C linker, remove when meson 0.55 is released # a regular meson run - - run: meson build && ninja -Cbuild test + - run: meson build && ninja -j9 -Cbuild test # test a meson based dist - run: meson dist -Cbuild && rm -rf build # test experimental APIs - - run: meson build -Dexperimental_api=true -Dbenchmark=true -Dexperimental_api=true -Doptimization=2 && ninja -Cbuild test # or meson test -Cbuild + - run: meson build -Dexperimental_api=true -Dbenchmark=true -Dexperimental_api=true -Doptimization=2 && ninja -j9 -Cbuild test # or meson test -Cbuild # run benchmarks - run: build/perf/perf && meson test -Cbuild --benchmark && rm -rf build # or ninja -Cbuild benchmark # mingw