rajames/LithosAnanke
1
1
Fork 0
Code Issues 63 Pull Requests Actions Packages Projects Releases Activity

acceptance prints the serial log of a failed check (#136); the demo limits its guests (#116) #148

Merged
rajames merged 3 commits from StarForth-v4.0.0 into master 2026-11-08 00:07:46 +00:00
Conversation 0 Commits 3 Files Changed 7
+119 -12
3 Commits
Author SHA1 Message Date
Claude 1e3f211daa FABRIC-3 XLVIII: the review, the protocol, the SDK, the demo's limits
Build / Image RASPI (push) Canceled after 0s
Details
Build / Image PC (push) Canceled after 0s
Details
Build / Image MILKV (push) Canceled after 0s
Details
Build / v4 tests (32- and 64-bit cells) (push) Canceled after 0s
Details
Acceptance / Acceptance (pull_request) Successful in 16m20s
Details 
Today's rulings and work since XLVII.6, kept at the pace of the work
(Captain Bob, 2026-11-07: 'the book of fabric needs to keep pace'): the
alpha.4 list (#147) and what is in it, the developer protocol (#135), the
Book of Fabric (#138), the SDK milestone with the capsule repository (#149)
and the latency DoE (#150), #136 and the demo's guests and busy message,
with what was measured.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GE3SDvQn5EoxdGufk84zz2
 2026-11-07 23:19:28 +00:00
Claude 171b3947dd demo: two guests of 384 MiB, and a busy message for the rest (#116)
Build / Image RASPI (push) Canceled after 0s
Details
Build / Image PC (push) Canceled after 0s
Details
Build / Image MILKV (push) Canceled after 0s
Details
Build / v4 tests (32- and 64-bit cells) (push) Canceled after 0s
Details
Acceptance / Acceptance (pull_request) Canceled after 0s
Details 
Captain Bob, 2026-11-07: 'Limit guests and have a Busy, try back in a few
minutes.' start-session.sh takes one of DEMO_MAX_GUESTS slots (default 2),
a lock it holds for the session's life (flock -n: two visitors cannot both
take the last one; QEMU and the bridge are started without its descriptor);
with every slot taken, the visitor's terminal says every machine is busy and
to try back in a few minutes, and the session ends without a machine. The
service: DEMO_MAX_GUESTS=2, RuntimeDirectory for the locks, ttyd's
--max-clients 6 so a visitor over the limit reaches the message. The guest:
384 MiB (v4 boots from 256 MiB, refuses at 128; measured, #116). Tested
here: every slot held -> the busy message; slot 1 held -> slot 2 taken.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GE3SDvQn5EoxdGufk84zz2
 2026-11-07 23:18:40 +00:00
Claude 1d4898496f acceptance: a failed check prints the serial log where it looked (#136)
Build / Image PC (push) Successful in 3m20s
Details
Build / v4 tests (32- and 64-bit cells) (push) Successful in 10m1s
Details
Build / Image MILKV (push) Successful in 2m55s
Details
Build / Image RASPI (push) Successful in 2m42s
Details
Acceptance / Acceptance (pull_request) Successful in 18m44s
Details 
Run 197's riscv64 failure (#131) could only be read from the run's logs
artifact, which Gitea's API does not list. qemu_session.py's check() now
prints, on a FAIL, the serial lines after the first match of an anchor the
check names, or the log's last lines; control characters as escapes, so a
stray byte or terminal sequence in a line shows instead of only failing a
match. The boot-disk checks anchor on 'Boot successful!'. A passing run
prints as before (riscv64 here, logs/ committed).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GE3SDvQn5EoxdGufk84zz2
 2026-11-07 22:49:03 +00:00