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).
2 files changed, 2 insertions(+), 0 deletions(-)
ci/x86_64-linux-debug.sh+1
| ... | ... | @@ -58,6 +58,7 @@ stage3-debug/bin/zig fmt --check .. \ |
| 58 | 58 | stage3-debug/bin/zig build -Dtarget=arm-linux-musleabihf |
| 59 | 59 | |
| 60 | 60 | stage3-debug/bin/zig build test docs \ |
| 61 | --maxrss 21000000000 \ |
| 61 | 62 | -fqemu \ |
| 62 | 63 | -fwasmtime \ |
| 63 | 64 | -Dstatic-llvm \ |
ci/x86_64-linux-release.sh+1
| ... | ... | @@ -59,6 +59,7 @@ stage3-release/bin/zig fmt --check .. \ |
| 59 | 59 | stage3-release/bin/zig build -Dtarget=arm-linux-musleabihf |
| 60 | 60 | |
| 61 | 61 | stage3-release/bin/zig build test docs \ |
| 62 | --maxrss 21000000000 \ |
| 62 | 63 | -fqemu \ |
| 63 | 64 | -fwasmtime \ |
| 64 | 65 | -Dstatic-llvm \ |
Andrew Kelley <andrew@ziglang.org> 2023-04-17 10:38:27-07:00