summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPatrick Steinhardt <ps@pks.im>2025-02-26 09:22:23 +0100
committerJunio C Hamano <gitster@pobox.com>2025-02-26 09:09:37 -0800
commit9350423982a851695b8f0fab1fd7aa8fafb10654 (patch)
tree292c18a2a0f820ed4850f660fd1caebdd259f3d0
parent2c374ea4bb47c84f80f905df3a00b7d724386a28 (diff)
gitlab-ci: restrict maximum number of link jobs on Windows
The hosted Windows runners on GitLab.com only have 7.5GB of RAM. Given that "link.exe" provided by Microsoft Visual Studio is multi-threaded by itself already and thus quite memory hungry this can quickly lead to memory starvation, out-of-memory situations and thus failed CI jobs. Fix the issue by limiting the number of concurrent linker jobs. The same issue hasn't been observed on GitHub Actions yet, probably because it got more than twice the amount of RAM with 16GB. Signed-off-by: Patrick Steinhardt <ps@pks.im> Signed-off-by: Junio C Hamano <gitster@pobox.com>
-rw-r--r--.gitlab-ci.yml2
1 files changed, 1 insertions, 1 deletions
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 4976e18a05..7e1cecc6a7 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -169,7 +169,7 @@ build:msvc-meson:
extends: .msvc-meson
stage: build
script:
- - meson setup build -Dperl=disabled
+ - meson setup build -Dperl=disabled -Dbackend_max_links=1
- meson compile -C build
artifacts:
paths: