ScottW514
d4e2f85538
wait_idle returned on a stale Idle before a just-commanded move began, and the tests declared PASS on grblHAL's Idle while the kernel still played the stream depth and the decel tail (the baseline caught state=running after motion.pacing). Every motion test now ends on forgectrl's idle (machine_idle), and wait_idle ignores an Idle inside a short grace unless a non-Idle state was seen. status_report re-sends '?' every 0.5 s until a report arrives: a soft reset (^X) flushes the controller's read buffer and eats a '?' that lands in it - the bench saw motion.cancel-abort error with no report for 5 s after the abort while the controller answered the next '?' at once. motion.deadman: the SIGSTOP drill waited for a running controller and got the killed pid back before the supervisor reaped it (drill 1 already waited for a different pid); and the forgectrl-restart drill expected the busy controller's pid to survive the retake, but a retake under the broker is stop-at-idle, re-probe, start a supervised controller (the old inherited fd cannot be adopted) - the check is now: the move finished unmanaged, supervision came back running and verified. Bench-proven 2026-08-16: kill respawn 1.3 s, hang -> underrun 0.21 s, retake at idle.
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
docs/ACCEPTANCE.md.
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>:8080 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_MARKER |
/run/forgetest.active |
takeover marker |
FORGECTRL_URL, FORGECTRL_TOKEN_FILE |
http://127.0.0.1:8080, /data/forgefirm/panel.token |
forgectrl client |
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, 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.