Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 20 additions & 0 deletions issues/a-boots-readback-is-lost-to-one-ssh-that-times-out.md
Original file line number Diff line number Diff line change
Expand Up @@ -25,6 +25,26 @@ exchange`; the next boot's flash followed. Its four rows
image (sha256 checked), booted again, was judged green on all four. The development
machine's network dropped in the same minutes.

- **Owed on metal:** the T14 has not run the loop's `ssh` bounds and keepalive
(pull request #1255), which change every `ssh` this loop runs. The rows are
the T14's two flashes of `boot:testcases`, `testcases` and
`testcases-watchdog`. Each `toyos-metal` log of main must show:
- `toyos-metal` exiting 0 or 1, never 2, with no `Expired` and no `Untaken`;
- `run: echo rebooting && sudo -n '/usr/sbin/reboot'`, then either a clean
answer or `ssh failed itself once the machine had started the reboot
(…); it is ridden`, then a readback;
- `dd took X s of its Y s bound` for every piece, the smallest margin
recorded.

The judge of `wall_clock_is_firmwares` is owed on both benches: it must not
be red on its window, which counts `down` from the reboot's ask.

The AMD bench's two flashes ran through that head on 2026-11-11 and showed
the rest: exit 0, a clean answer to the reboot, and the largest share of a
bound any piece took was 17.4 s of 1208 s
(https://github.com/ToyOSOrg/evidence/tree/84a22513e1debd0779794eddc7b326ea3fcb4160/metal).
Their readbacks were deleted before a judge read them.

Owner: the orchestrator, which holds the T14. **Exit**: a dial lost while
the stick is being read costs a retry bounded by a timeout that fails loudly,
not the boot, or the stick's log partition is copied off whole before anything
Expand Down
Loading