From f53ec2d71d8c53ebdf44b8d17b693e798aba50ab Mon Sep 17 00:00:00 2001 From: Sebastian Date: Sat, 3 Oct 2026 19:41:09 +0200 Subject: [PATCH] Fix: ulimit and odin test must be on the same justfile line just runs each recipe line in its own shell invocation (no shebang on this recipe), so the previous commit's separate ulimit -s 8192 line never actually affected the odin test line - CI segfaulted again the same way. Confirmed fixed in an ubuntu:24.04 container running the actual `just test` recipe with ulimit -s unlimited set beforehand. Co-Authored-By: Claude Sonnet 5 --- justfile | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/justfile b/justfile index 16d3969..b31d541 100644 --- a/justfile +++ b/justfile @@ -32,8 +32,9 @@ test: # Odin's core:thread passes that straight to pthread_attr_setstacksize, pthread_create # then fails, and thread.create() returns nil - which core:testing's pool_init # dereferences unconditionally, segfaulting the whole test binary. Clamp it. - ulimit -s 8192 - odin test tests -vet -define:ODIN_TEST_THREADS=1 -out:{{build_dir}}/tests + # (One line: just runs each recipe line in its own shell, so a separate + # `ulimit` line wouldn't carry over to the `odin test` line.) + ulimit -s 8192 && odin test tests -vet -define:ODIN_TEST_THREADS=1 -out:{{build_dir}}/tests # Optimized native build into build//, with the assets it needs at runtime release: