Skip to content

v4test: optional local transport in place of ash and acp - #56

Merged
WDrijver merged 1 commit into
mainfrom
tools/v4test-local-transport
Nov 16, 2026
Merged

WDrijver merged 1 commit into
mainfrom
tools/v4test-local-transport

Conversation

@WDrijver

Copy link
Copy Markdown
Contributor

What

tools/v4/v4test.py can use an optional machine-local transport module in place of ash and acp, to run the commands on the V4 and to upload the test programs.

  • The module is $AKB_V4_TRANSPORT, or by default ~/.config/akb/v4transport.py. It defines available(host), alive(host), run(host, cmd, timeout) -> (output, finished) and upload(host, path, remote_dir).
  • v4test.py uses it only when it loads and available() says the V4 answers. When it is missing, fails to load or raises, v4test.py uses ash and acp exactly as before. Nobody without such a module sees any change.
  • A module must never raise once a test has started, so a fallback to ash can never run a test twice.
  • summary.json records which transport ran ("local module" or "ash").

Why

A developer can drive the test V4 with another remote tool than ApolloExplorer, without a fork of v4test.py. Power cycling (Tasmota), HDMI capture and the serial log stay v4test.py's own: os-takeover tests still need them.

Tested

  • On the test V4 (V4 UniCorn, core 12856, ApolloOS R9.5) through a local module: add-mem-dbra, moviw and fpu-m68881 (both variants) all passed, summary.json says "local module".
  • Without a module, and with a module whose available() fails: alive() falls back to ash.
  • python tools/v4/v4test.py build builds all tests; check_frontmatter.py and check_links.py: OK.

Knowledge base files relied on

  • tools/v4/v4test.py
  • guides/testing-on-v4-hardware.md
  • CONTRIBUTING.md (section 10, CI checks and tests on V4 hardware)

🤖 Generated with Claude Code

A machine-local module ($AKB_V4_TRANSPORT, default
~/.config/akb/v4transport.py) can run the commands and upload the
programs. It is used only when it loads and its available() says the V4
answers; when it is missing, fails or raises, v4test.py uses ash and acp
as before. It never raises once a test has started, so a fallback never
runs a test twice. summary.json records which transport ran.

Tested on the test V4 (core 12856, ApolloOS R9.5): add-mem-dbra, moviw
and fpu-m68881 (both variants) passed through a local module, and with
none, alive() falls back to ash.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@WDrijver
WDrijver requested a review from TuKo1982 as a code owner November 16, 2026 16:38
@WDrijver
WDrijver merged commit e0e4556 into main Nov 16, 2026
2 checks passed
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