mirror of
https://github.com/openglow-org/forgefirm.git
synced 2026-10-16 01:29:55 -07:00
ScottW514
205f9f22f2
- forgectrl c274f19 -> c9e3347 (0.1.30 -> 0.1.31): setup is required up to the intake fans and recommended after, the coolant flow calibration is a required step, the TEC check gives way to the operator's answer, the head's id is head/info's "id" line, the intake fan count is decided in wizcalc, and the burns hand the lens back referenced; every start logs its firmware and slot, and every update job is logged; the beam sensor is recorded and logged; the panel's emission help parses again. The daemon starts on a host with its machine paths, release URLs and controller binaries from the environment, and the host cases for the routes, the tokens, the setup, the logs, the extension host and the cooling engine run through it in CI. - forgefirm-app 021323d -> 0f59c54 (0.1.31+git -> 0.1.32+git): the python3-gfhardware head, host tests only; it moves with the BSP's python3-gfhardware pin. - kas lock: meta-openglow f012d8e -> b7626be, the head that pins the kernel module f924cd9, python3-gfhardware 0f59c54 and gfutilities 993f9e1. grblHAL-glowforge keeps b34636f here: its CI runs this repository's harnesses from master, and its head's mcode_test expects the 5 s host build, so the driver is pushed after this and pinned on its own. Proof: image 20261015101725 carried forgectrl c9e3347, the module f924cd9 and this tree's forgetest, and campaign c-20261015103714-0c91 passed all 53 catalog tests on it with none inherited. bitbake -c fetch of forgectrl, gfcloud, gfhome, python3-ffmachine, python3-gfhardware, python3-gfutilities and kernel-module-glowforge from these pins succeeds (14 tasks). The tree manifest from the pins holds forgectrl at c9e3347 (229 files); the coverage lint over it finds no uncovered path, no empty entry and no host-tested row problem (53 tests); check-ui-vendor finds the shared UI files identical at c9e3347; test_tree_manifest passes, and the gate self-check refuses the empty artifact (rc 1).