Skip to content

fork-ci: raise the test thread stack to 8 MiB - #15

Merged
thedancingdeveloper merged 1 commit into
fork/mainfrom
fork/ci-stack
Oct 9, 2026
Merged

thedancingdeveloper merged 1 commit into
fork/mainfrom
fork/ci-stack

Conversation

@thedancingdeveloper

Copy link
Copy Markdown

Summary

  • `cargo test -p codex-core` aborts with `fatal runtime error: stack overflow` (seen on Let spawn_agent carry an output schema #10, run 37947101661).
  • Upstream sets `RUST_MIN_STACK: "8388608"` on its test step (`.github/workflows/rust-ci.yml`). The `cargo test` step here now sets the same 8 MiB floor.

Test plan

cargo test -p codex-core aborts with "fatal runtime error: stack overflow"
on the runner's default thread stack. Upstream sets RUST_MIN_STACK to 8 MiB
on its test step in rust-ci.yml, and fork-ci now does the same.

@thedancingdeveloper thedancingdeveloper left a comment

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review: no blockers (head 1b40b84)

One commit on fork/main that adds RUST_MIN_STACK: "8388608" to fork-ci's cargo test step, matching upstream (rust-ci.yml:158). It fixes the codex-core stack overflow seen in #10's run 37947101661. Merge condition: its own fork-ci run is green. A workflow-only PR has no changed crates, so check/fmt/clippy/test are quick. After merge, re-run fork-ci on #10.

@thedancingdeveloper
thedancingdeveloper merged commit feaf20e into fork/main Oct 9, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant