fix(ci): set RUST_MIN_STACK=16777216 to avoid rustc SIGSEGV #8

Merged

sameh-farouk merged 1 commit from development_sameh into development

2026-06-02 14:59:43 +00:00

sameh-farouk commented

2026-06-02 14:43:49 +00:00

Member

Summary

CI run #20 (bca78a14, push to development after PR #6 merge) failed with rustc SIGSEGV:

   Compiling hero_lifecycle v0.6.0 (...hero_lib.git?branch=development#d1383f58)
   Compiling herolib_ai v0.6.0 (...hero_lib.git?branch=development#d1383f58)
error: rustc interrupted by SIGSEGV, printing backtrace
help: you can increase rustc's stack size by setting RUST_MIN_STACK=16777216
error: could not compile `lab` (lib)

Default rustc thread stack is 8 MB. The hero_lib derive-heavy crates (openrpc/lifecycle macro expansion) blow that non-deterministically — run #19 on the same code state via development_sameh succeeded, run #20 on the same content via development push failed.

Fix

Set RUST_MIN_STACK=16777216 at job scope so every rustc invocation across all workflow steps (Install lab, Build + upload) gets the 16 MB stack.

Cross-repo concern

This class of fix likely applies to every hero_ repo's lab-publish workflow* — same upstream derive expansion happens in every consumer. Worth pushing into the canonical template in hero_skills once verified here.

Verification

Can't dispatch a new run reliably right now — runner queue is congested (run #21 has been stuck waiting for 50+ min). Next legitimate dev push will exercise this and confirm. Alternatively, dispatch manually post-merge once the queue clears.

## Summary CI run #20 (`bca78a14`, push to development after PR #6 merge) failed with rustc SIGSEGV: ``` Compiling hero_lifecycle v0.6.0 (...hero_lib.git?branch=development#d1383f58) Compiling herolib_ai v0.6.0 (...hero_lib.git?branch=development#d1383f58) error: rustc interrupted by SIGSEGV, printing backtrace help: you can increase rustc's stack size by setting RUST_MIN_STACK=16777216 error: could not compile `lab` (lib) ``` Default rustc thread stack is 8 MB. The hero_lib derive-heavy crates (openrpc/lifecycle macro expansion) blow that non-deterministically — run #19 on the same code state via `development_sameh` succeeded, run #20 on the same content via `development` push failed. ## Fix Set `RUST_MIN_STACK=16777216` at job scope so every rustc invocation across all workflow steps (`Install lab`, `Build + upload`) gets the 16 MB stack. ## Cross-repo concern This class of fix likely applies to **every hero_* repo's `lab-publish` workflow** — same upstream derive expansion happens in every consumer. Worth pushing into the canonical template in `hero_skills` once verified here. ## Verification Can't dispatch a new run reliably right now — runner queue is congested (run #21 has been stuck `waiting` for 50+ min). Next legitimate dev push will exercise this and confirm. Alternatively, dispatch manually post-merge once the queue clears.

sameh-farouk added 1 commit

2026-06-02 14:43:49 +00:00

fix(ci): set RUST_MIN_STACK=16777216 to avoid rustc SIGSEGV 9d8dd6f500

CI run #20 (bca78a14) failed with rustc SIGSEGV compiling
hero_lib's derive-heavy crates (`hero_lifecycle`, `herolib_ai`):

  error: rustc interrupted by SIGSEGV, printing backtrace
  /root/.rustup/toolchains/1.96-x86_64-unknown-linux-gnu/lib/...
  help: you can increase rustc's stack size by setting
        RUST_MIN_STACK=16777216
  error: could not compile `lab` (lib)

Default rustc thread stack is 8 MB; derive expansion in the hero_lib
openrpc/lifecycle stack blows it non-deterministically (run #19 on
development_sameh succeeded with identical code).

Setting RUST_MIN_STACK=16777216 at job scope so every rustc
invocation across all steps (`Install lab`, `Build + upload`) gets
the 16 MB stack.

Class of fix likely applies to every hero_* repo's lab-publish
workflow — worth pushing into the hero_skills template.