From fe3c3aed3115234ec7ffc284278181c56240756b Mon Sep 17 00:00:00 2001 From: funman300 Date: Tue, 7 Jul 2026 17:33:36 -0700 Subject: [PATCH] fix(ci): cap cargo to two parallel jobs so concurrent test-binary links fit runner memory MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Runs 514/516/519 (incl. master itself) died on 'ld terminated with signal 9' — the workspace now links enough large test binaries that per-core parallel linking OOMs the runner even at line-tables-only debuginfo. CARGO_BUILD_JOBS=2 keeps at most two links in flight. Co-Authored-By: Claude Fable 5 --- .gitea/workflows/test.yml | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/.gitea/workflows/test.yml b/.gitea/workflows/test.yml index 25f1e13..73f51ed 100644 --- a/.gitea/workflows/test.yml +++ b/.gitea/workflows/test.yml @@ -35,8 +35,15 @@ jobs: # runner's memory — ld was OOM-killed (signal 9) on runs 447 and 486. # line-tables-only keeps file:line in panic backtraces while cutting the # link's memory footprint enough to fit the runner. + # + # CARGO_BUILD_JOBS=2: with one job per core, cargo links several large + # test binaries concurrently; as the workspace grew (runs 514/516/519) + # two+ simultaneous ld processes OOM-killed the runner again even at + # line-tables-only. Two jobs keeps at most two links in flight — the + # compile-throughput cost is small next to the cache-warm build. env: CARGO_PROFILE_DEV_DEBUG: line-tables-only + CARGO_BUILD_JOBS: '2' steps: - name: Checkout