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).
This commit is contained in:
Andrew Kelley 2023-04-17 10:38:27 -07:00
parent 17af53554e
commit 2d41dac57d
2 changed files with 2 additions and 0 deletions

View file

@ -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 \

View file

@ -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 \