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

rajames commented 2026-11-07 22:49:18 +00:00

Owner

Copy Link

Copy Source

What and why

When an acceptance check fails, scripts/qemu_session.py now prints the serial log where the check looked, into the job's output: the lines after the first match of an anchor the check names, else the log's last lines. Control characters are shown as escapes (\x1b[...), so a stray byte or terminal sequence inside a line is visible instead of only failing a match. The boot-disk checks anchor on Boot successful!.

Run 197's riscv64 failure (#131) could only be read from the run's logs artifact, which Gitea's API does not list; the next failure explains itself in the log.

Closes #136. Part of #131.

Also (171b3947): the demo -- two guests of 384 MiB (#116: v4 boots from 256 MiB, refuses at 128), and a visitor over the limit gets "Every StarshipOS machine is busy right now ... Try back in a few minutes." in the terminal, not a dead connection (start-session.sh slot locks; the service: DEMO_MAX_GUESTS=2, RuntimeDirectory, --max-clients 6). Takes effect when the demo is deployed (#115).

Acceptance

The Acceptance check runs on this pull request -- also the first full run with both wikis up (alpha.4's first server test).

• Logs committed: a riscv64 acceptance here with the new script, passing and printing as before; excerpt() run against a real riscv64 serial log, with an anchor and without
• Hardware this was tried on, if any: none

The record

• docs/fabric/FABRIC-3.md -- not design work
• CHANGELOG.md -- not a milestone
• Nothing in this PR is a fix nobody asked for (.claude/CLAUDE.md, Hard Rules) -- #136, asked for 2026-11-07

🤖 Generated with Claude Code

https://claude.ai/code/session_01GE3SDvQn5EoxdGufk84zz2

## What and why When an acceptance check fails, `scripts/qemu_session.py` now prints **the serial log where the check looked**, into the job's output: the lines after the first match of an anchor the check names, else the log's last lines. Control characters are shown as escapes (`\x1b[...`), so a stray byte or terminal sequence inside a line is visible instead of only failing a match. The boot-disk checks anchor on `Boot successful!`. Run 197's riscv64 failure (#131) could only be read from the run's `logs` artifact, which Gitea's API does not list; the next failure explains itself in the log. Closes #136. Part of #131. **Also (171b3947): the demo** -- two guests of 384 MiB (#116: v4 boots from 256 MiB, refuses at 128), and a visitor over the limit gets "Every StarshipOS machine is busy right now ... Try back in a few minutes." in the terminal, not a dead connection (start-session.sh slot locks; the service: DEMO_MAX_GUESTS=2, RuntimeDirectory, --max-clients 6). Takes effect when the demo is deployed (#115). ## Acceptance The **Acceptance** check runs on this pull request -- also the first full run with both wikis up (alpha.4's first server test). - [x] Logs committed: a riscv64 acceptance here with the new script, passing and printing as before; `excerpt()` run against a real riscv64 serial log, with an anchor and without - [ ] Hardware this was tried on, if any: none ## The record - [ ] `docs/fabric/FABRIC-3.md` -- not design work - [ ] `CHANGELOG.md` -- not a milestone - [x] Nothing in this PR is a fix nobody asked for (`.claude/CLAUDE.md`, Hard Rules) -- #136, asked for 2026-11-07 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01GE3SDvQn5EoxdGufk84zz2

rajames added this to the v4.0.0-alpha.4 milestone 2026-11-07 22:49:18 +00:00

rajames added 1 commit 2026-11-07 22:49:19 +00:00

acceptance: a failed check prints the serial log where it looked (#136) ... 1d4898496f

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

rajames added 1 commit 2026-11-07 23:18:44 +00:00

demo: two guests of 384 MiB, and a busy message for the rest (#116) ... 171b3947dd

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

rajames changed title from acceptance: a failed check prints the serial log where it looked (#136) to acceptance prints the serial log of a failed check (#136); the demo limits its guests (#116) 2026-11-07 23:18:50 +00:00

rajames added 1 commit 2026-11-07 23:19:31 +00:00

FABRIC-3 XLVIII: the review, the protocol, the SDK, the demo's limits ... 1e3f211daa

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

rajames merged commit 6bbf4b1afd into master 2026-11-08 00:07:46 +00:00

rajames referenced this issue from a commit 2026-11-08 00:08:03 +00:00

demo: DEPLOY.md, the server checklist for Try it [skip ci]

rajames referenced this pull request 2026-11-08 00:38:40 +00:00

Gitea: a push to an open PR's branch can take 1.75 GB (patch test and diff statistics) #152

Sign in to join this conversation.

Reviewers

No Reviewers

Labels

Clear labels

area/capsules

capsules/ and mkcapsule

area/docs

docs/

area/kernel

kernel/ -- LithosAnanke

area/proofs

proof/ -- Isabelle/HOL

area/v3

v3/ -- the original StarForth VM

area/v4

v4/ and capsules/v4 -- the F18 engine

board/milkv

Milk-V Mars

board/pc

Generic x86-64 PC (SER5)

board/raspi4

Raspberry Pi 4 (not ported)

board/raspi5

Raspberry Pi 5

board/zynq7020

Zynq-7020 (ARMv7 port in progress)

kind

bug

Something is wrong

kind

chore

Housekeeping, repo hygiene

kind

ci

Build, CI, nightly, release

kind

docs

Documentation only

kind

feature

New capability

priority

must

Needed for v4.0.0 (JUSTIFICATION.md 14/16)

priority

nice

Nice to have

priority

should

Needed for the product, not for the tag

status

backlog

Not started

status

blocked

Waiting on something else

status

in-progress

Being worked on

status

needs-acceptance

Done; the QEMU acceptance boots are still to run

status

rejected

Decided against; closed

No labels

Milestone

No items

No Milestone v4.0.0-alpha.4

Projects

Clear projects

No projects

Assignees

Clear assignees

rajames (Robert A. James (Captain Bob))

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: rajames/LithosAnanke#148