zig

commit 2d41dac57d3afdd5fe3d03be08ff0a24833f61dd (tree)
parent 17af53554e1362f9632aff592afcba11190c94b1
Author: Andrew Kelley <andrew@ziglang.org>
Date:   Mon, 17 Apr 2023 10:38:27 -0700

CI: give x86_64-linux a maxrss parameter

to avoid getting OOM killed. It's been happening regularly recently. We
need to have a high number of GitHub Actions runners simultaneously
active, otherwise the hardware ends up underutilized. But with zig build
running in parallel now, this sometimes results in memory usage spikes
that have been causing the runner to get killed.

This number is the total physical memory (126G) divided by the number of
runners we have active (6).

Diffstat:
M
ci/x86_64-linux-debug.sh
 | 
1
+
M
ci/x86_64-linux-release.sh
 | 
1
+

2 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/ci/x86_64-linux-debug.sh b/ci/x86_64-linux-debug.sh
@@ -58,6 +58,7 @@ stage3-debug/bin/zig fmt --check .. \
 stage3-debug/bin/zig build -Dtarget=arm-linux-musleabihf
 
 stage3-debug/bin/zig build test docs \
+  --maxrss 21000000000 \
   -fqemu \
   -fwasmtime \
   -Dstatic-llvm \
diff --git a/ci/x86_64-linux-release.sh b/ci/x86_64-linux-release.sh
@@ -59,6 +59,7 @@ stage3-release/bin/zig fmt --check .. \
 stage3-release/bin/zig build -Dtarget=arm-linux-musleabihf
 
 stage3-release/bin/zig build test docs \
+  --maxrss 21000000000 \
   -fqemu \
   -fwasmtime \
   -Dstatic-llvm \