Build Loom single-threaded (-j1) to avoid failed to create thread in CI#13
Draft
astefano wants to merge 1 commit into
Draft
Build Loom single-threaded (-j1) to avoid failed to create thread in CI#13astefano wants to merge 1 commit into
Loom single-threaded (-j1) to avoid failed to create thread in CI#13astefano wants to merge 1 commit into
Conversation
The `Loom` lib passed `--tstack=100000000` (100 MB per worker thread). On a CI runner the default worker pool requests that stack and thread creation fails (`failed to create thread`, building Loom.LatticeExt). Use `-j1` instead, which avoids the oversized per-thread stacks. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #12.
The
Loomlib passed--tstack=100000000(100 MB per worker thread). On a CI runner the default worker pool requests that stack and thread creation fails:This swaps it for
-j1(single-threaded), avoiding the oversized per-thread stacks. Thequangvdao/loom2fork made the same change (ci: avoid oversized Lean thread stacks/ci: compile Loom modules single-threaded).Verified on my fork together with #9 (workflow location) and #11 (toolchain pin): full green build, 22/22 jobs incl.
Loom,Main, and theloom2exe. This is the last of the three CI blockers — #9 + #11 + this together get CI green.