igneum-network/igneum
1
0
Fork 0
Code Issues Pull requests Releases Activity

CLAUDE.md: builds and test suites run on the PCs through build jobs; the Mac builds only macOS binaries

Browse source 
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
igneum-josh 2026-10-05 09:53:17 +01:00
parent b82ff11779
commit f378aa02e6
1 changed files with 7 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
CLAUDE.md
View file

@ -57,6 +57,13 @@ Every Igneum task in Claude in Chrome runs in the Chrome profile "josh (igneum.n
harnesses and simulators whose outputs are counts, locks, forks or seconds, and lets builds continue; use the MAIN
checkout's script, /Users/joshm/Projects/igneum/tools/lock/with-lock.sh, from any worktree). A number taken while
another build or simulation ran is not a number.
- Builds and test suites run on the PCs, not on this Mac (standing rule, 5 October 2026, Josh: "since building on the pc is so
much faster, lets fully utilise both of them"): Linux and Windows binaries and every cargo test suite go out as `build` jobs
(`node tools/build-job.mjs run --target ae432dc7|1ccfe586 ...`, PC 1 = ae432dc7 for builds, PC 2 = 1ccfe586 for test
suites; one job per machine at a time; results come back through the relay, every sha256 checked). Measured 5 October:
PC 1 built the Linux and Windows node and app and ran both test suites in 7 min 38 s cold, 5 min 09 s warm. The Mac
builds only the macOS binaries and the DMG, under the build lock, and `~/.config/igneum/build-slots` (1 to 3) caps how
many Mac builds run at once.
- Every agent works in its own git worktree (`git worktree add ../igneum-wt-<name>`), never the shared checkout, and
stages only its own files. Builds: `nice -n 19`, at most 4 cargo jobs. Windows builds go to the GitHub runner, Linux
binaries come from `infra/cross/build-linux.sh`; nothing is built on a server.