Skip to content

Ci/docs and busy beaver sharding - #31

Open
mo271 wants to merge 2 commits into
mainfrom
ci/docs-and-busy-beaver-sharding
Open

mo271 wants to merge 2 commits into
mainfrom
ci/docs-and-busy-beaver-sharding

Conversation

@mo271

@mo271 mo271 commented Nov 11, 2026

Copy link
Copy Markdown
Collaborator

No description provided.

… cache loop

- Target Cryptids, BusyBeaverChallenge, and human-authored BusyBeaver framework/hardness/landmark modules in literate.toml (121 rendered modules vs 431), avoiding multi-hour single-threaded SubVerso elaboration on raw generated M_* scripts and 49k-line Calculi blobs.
- Compute minimal lake build targets from literate.toml so lean-action compiles only documented modules and their transitive dependencies (6.5 MiB vs 25.6 MiB).
- Split actions/cache into restore + save (persisting partial .lake/build/literate progress on step timeout) to prevent cold-cache timeout loops, add concurrency + paths-ignore filters, reclaim build disk space before Pages upload, and pin action SHAs.
- Partition BusyBeaver's DAG dynamically into a cached foundation job (BusyBeaverChallenge + non-leaf modules, incl. Calculi and shared donor M_* files), 8 parallel crc32-keyed leaf shards with independent .lake/build/{lib/lean,ir} zstd caches, and a final build job that reassembles artifacts with zero recompilation and runs lake comparator inside bubblewrap.
- Preserve the exact 'BusyBeaver CI / build' check run name for branch protection.

This branch has not been deployed

No deployments
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