docs: state the c64-test-harness prerequisite on the UCI path (#90) - #91
Merged
Conversation
A contributor built with `make BACKEND=uci`, ran a tools/uci/ script, and hit ModuleNotFoundError: No module named 'c64_test_harness'. The instruction existed — README.md's VICE testing section has `pip install -e ../c64-test-harness` — but neither the "Ultimate 64 Elite Hardware Tests" section nor CLAUDE.md's "UCI test scripts" section mentioned it. Both go straight from `make BACKEND=uci` to invoking scripts, so someone on the UCI path never crosses the line that would have told them. Same shape as the ip65 blob report: the information exists, just not on the path the reader is walking. Adds to both UCI sections: the harness is a separate public repo (not vendored; requirements.txt carries only cryptography), the clone + `pip install -e` commands, the exact error it prevents, and the note that it must go into the same interpreter used to run the scripts — a venv mismatch reproduces the identical failure after an install that looks successful. Reported-by: Armitage64 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This was referenced Aug 14, 2026
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Closes#90.
A contributor built with
make BACKEND=uci, ran atools/uci/script, and got:This is a documentation gap, not a bug. The instruction exists —
README.md:155haspip install -e ../c64-test-harness— but it lives in the general VICE testing section. Neither the "Ultimate 64 Elite Hardware Tests" section nor CLAUDE.md's "UCI test scripts" section mentions it; both go straight frommake BACKEND=ucito invoking scripts. Someone following the UCI path never crosses the line that would have told them.That is the same shape as the
ip65-c64.binreport fixed in #89 an hour earlier: the information is present in the repo, just not on the path the reader is actually walking. Two independent newcomers, two setup walls, both from following a documented route with a prerequisite documented elsewhere.What this adds
To both UCI sections:
requirements.txtcarries onlycryptography, which is why the wall isn't obvious)pip install -e ../c64-test-harnesscommandspython3, and a venv mismatch reproduces the identical failure after an install that appears to succeed🤖 Generated with Claude Code