[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.
This commit is contained in:
Ebrahim Byagowi 2020-06-29 00:19:38 +04:30 committed by GitHub
parent 831b090001
commit fd8b0a44c4
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions

View File

@ -222,11 +222,11 @@ jobs:
- run: pip3 install fonttools --upgrade - run: pip3 install fonttools --upgrade
- run: pip3 install git+https://github.com/mesonbuild/meson # use C linker, remove when meson 0.55 is released - run: pip3 install git+https://github.com/mesonbuild/meson # use C linker, remove when meson 0.55 is released
# a regular meson run # a regular meson run
- run: meson build && ninja -Cbuild test - run: meson build && ninja -j9 -Cbuild test
# test a meson based dist # test a meson based dist
- run: meson dist -Cbuild && rm -rf build - run: meson dist -Cbuild && rm -rf build
# test experimental APIs # 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 benchmarks
- run: build/perf/perf && meson test -Cbuild --benchmark && rm -rf build # or ninja -Cbuild benchmark - run: build/perf/perf && meson test -Cbuild --benchmark && rm -rf build # or ninja -Cbuild benchmark
# mingw # mingw