ScottW514
61652e237d
exthost.motion-job stayed in01f5991as the bench proof of machine_host_token() on the default token path. forgeext 31cdb40, the revisionc177aabpins, makes the token file overridable (FORGEEXT_HOST_TOKEN_FILE) and keeps /run/forgefirm/ext-host.token when the variable is unset or empty. The recipe's binary from that revision (sha256 15ca6003b59f69fb9eadf686094430fbbd25e7cc177230a0417738484fe3427e) ran on the bench reference with the variable unset, and exthost.platform, exthost.service, motion.jog-roundtrip and exthost.motion-job passed on it (campaign c-20261015103714-0c91): the package's job reached the machine as job:org.forgetest.reference through the credential read from the default file. Its paths, now: - forgectrl src/jobpost.*: tests/jobpost_test.c, POST /job's multipart reader (row added). - forgectrl src/tokens.*: tests/tokens_test.c, the scoped tokens and the extension host's credential file (row added). - forgectrl src/jobrun.*: still covered by the burn tests. - forgeext src/api.*, src/machine.*, src/run.*: still covered by exthost.service's forgeext/**. Both rows name tests forgectrl's build.yml runs at the pinned 22a2cfc. No other catalog test required exthost.motion-job. exthost.py's hw import went with it. Fingerprints: every exthost test moves with the module text. The next image owes exthost.service and exthost.armed-freeze for forgeext's source change. Proof: the coverage lint over the tree manifest from the pins finds 0 uncovered paths and 0 host-tested row problems (48 tests); pyflakes on the touched files is clean; forgetest's unit suite under Linux passes (327).
forgetest - the ForgeFIRM release acceptance tool
The daemon behind http://<machine>:8090/ on the dev image: runs the
acceptance catalog against the machine, keeps the append-only result log,
decides which results still apply to the image that is running, exports
the release artifact scripts/release.sh gates on, and serves the bench
diagnostics page. The contract - catalog, campaigns, fingerprints,
inheritance, the gate, the coverage rule - is
the Acceptance page of the documentation site.
Run the host tests
cd forgetest
python3 -m unittest discover -s tests -v
Run the daemon on a workstation (against a mock or a manifest file)
FORGETEST_DATA=/tmp/ft FORGETEST_MANIFEST=../tree-manifest.json \
FORGECTRL_URL=http://<machine> python3 -m forgetest --port 8090
scripts/manifest-from-tree.py produces tree-manifest.json from the recipe
pins; the coverage lint is python3 -m forgetest.coverage --manifest ....
Environment
| Variable | Default | Purpose |
|---|---|---|
FORGETEST_DATA |
/data/forgetest |
results.jsonl, bench.jsonl, token, export/ |
FORGETEST_MANIFEST |
/etc/forgefirm-manifest.json |
the image manifest |
FORGETEST_PORT, FORGETEST_HOST |
8090, 0.0.0.0 | listener |
FORGETEST_BENCH_DIR |
/usr/share/forgetest/bench |
the installed bench scripts |
FORGETEST_BENCH_DATA |
<FORGETEST_DATA>/bench |
passed to bench tools: where they keep their data files (with GF_HOST=127.0.0.1 and the panel token in GF_TOKEN) |
FORGETEST_MARKER |
/run/forgetest.active |
takeover marker |
FORGECTRL_URL, FORGECTRL_TOKEN_FILE |
http://127.0.0.1, /data/forgefirm/panel.token |
forgectrl client (HTTP; the token authorizes writes from the board) |
FORGECTRL_TLS_URL |
https://127.0.0.1 |
forgectrl over HTTPS (self-signed, unverified), for the login test |
GF_SYSFS_ROOT |
/sys/glowforge/ |
kernel module sysfs |
GRBL_HOST, GRBL_PORT |
127.0.0.1, 23 | Grbl TCP |
Adding a test
Register it in the subsystem module under forgetest/suite/ with
@test(...): id subsystem.name, kind, hardware, mode (the controller
mode the test needs; the runner switches to it first), covers,
requires, always, steps. The body gets a Context (log, check, fail,
prompt, confirm, instruct, sleep, evidence, forgectrl, sysfs,
grbl, takeover). Return normally for PASS, raise runner.Failed for
FAIL. Then run the unit tests and the coverage lint.