Repository navigation
v4test: optional local transport in place of ash and acp - #56
Merged
Merged
Conversation
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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
tools/v4/v4test.pycan use an optional machine-local transport module in place ofashandacp, to run the commands on the V4 and to upload the test programs.$AKB_V4_TRANSPORT, or by default~/.config/akb/v4transport.py. It definesavailable(host),alive(host),run(host, cmd, timeout) -> (output, finished)andupload(host, path, remote_dir).available()says the V4 answers. When it is missing, fails to load or raises, v4test.py usesashandacpexactly as before. Nobody without such a module sees any change.ashcan never run a test twice.summary.jsonrecords 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-takeovertests still need them.Tested
add-mem-dbra,moviwandfpu-m68881(both variants) all passed,summary.jsonsays"local module".available()fails:alive()falls back toash.python tools/v4/v4test.py buildbuilds all tests;check_frontmatter.pyandcheck_links.py: OK.Knowledge base files relied on
tools/v4/v4test.pyguides/testing-on-v4-hardware.mdCONTRIBUTING.md(section 10, CI checks and tests on V4 hardware)🤖 Generated with Claude Code