firmware

309 Commits 8 Branches 8 Tags

2 Commits

Include renames

Author SHA1 Message Date

Author	SHA1	Message	Date
Oleksandr ShyshatskyiandClaude Opus 5	56b5b6c334	The printer image is the only replica; make rootfs was a second way nothing took `make rootfs` unsquashed rootfs.squashfs out of the stock package into work/rootfs, and a thin container bind-mounted it with PROG_DUMP supplying /usr/prog from the factory image. Every caller set PRINTER_IMAGE anyway -- both workflows wrote it into test.env BEFORE running `make rootfs`, so CI unpacked a 93MB package, unsquashed a rootfs and downloaded a 182MB factory image on every push and read none of it. build-printer-image.sh never used work/rootfs either: Dockerfile.full does its own extraction from the same public firmware and needs no stock package at all. So the fallback went, and PROG_DUMP with it -- it was only ever read when the replica was built locally, and both implementations already passed it empty otherwise. Gone: the target, extract-rootfs.py, gates.extract_rootfs and its two tar helpers, the thin printer/Dockerfile, the `prebuilt` flag threaded through both Replica implementations, and Replica.start's want_output, whose only message was that the local build was about to be slow. PRINTER_IMAGE is pinned to 1.9.7-1.2.9-20260810 rather than :latest. It is now the entire substrate the brick-safety gates run on and the only input nothing checksums, so a floating tag would let it change under a green suite -- the drift the sha256 pins in both workflows exist to prevent. THREE THINGS THAT COULD NOT HAVE PASSED, found while doing it: * Neither workflow built the feed. bin/patch.sh has refused to start without one since `a1b4ea6`, 45 commits after ci.yml was last touched. Both ran unpack/patch/pack straight into that guard. * `make release` ran bin/build.sh on $(RUN), which has no docker socket, while patch.sh assembles the payload inside the replica. `build` has used RUNBUILD all along; `release` was left behind. It also built no feed. It now builds one, once, outside the per-model loop -- nothing in it is model-specific. * ci.yml's shellcheck gate named pkgs//payload/init.d/S and pkgs//prog/.sh, neither of which exists any more; shellcheck exits 2 on a path it cannot open. It is a `find` with an asserted count now, because the opposite failure is worse: a glob that quietly matches nothing checks nothing and still reports green. Both workflows now go through `make` instead of hand-rolling `docker run`. Hand-rolling meant CI exercised entry points no human uses, which is exactly why the `release` runner bug could sit there unseen; it also ran as root and left a work/ that the later `make release` could not write to. ci.yml's test job builds the feed before the static lane. A good part of that lane asks what is inside an .ipk and those questions do not fail without one -- they return, and the lane reports a pass having never opened a package. build-packages.sh needs no stock firmware, which is what makes that possible. Docs, and the packages skill, which still documented pkg_buildopkg and work/.opkg-host as how the payload is assembled -- the host opkg went in `dcd037c` and the printer's own installs the feed now -- and still claimed qa/static holds an ABI gate over every ELF in every package. It does not: qa/replica/test_abi.py is the only one, and qa/static asserts a seventh does not grow back. Verified: qa/static is 122 passed / 110 errors here, identical to master -- every error is `vendor/opkg-utils is missing` in a checkout that has not run `make vendor`. mkdocs build --strict passes. The new shellcheck gate was run as written. The workflows themselves were not executed. tools/replica/printer/*.sh live inside the published image, so those edits take effect on the next `make printer-image`; behaviour is unchanged either way, because nothing sets PROG_DUMP any more. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TrhjKabxDihvVjNQGGT4MK	2026-08-30 14:56:26 +03:00
Oleksandr ShyshatskyiandClaude Opus 5	c185ef3285	The replica is a build tool; test/ is 28 unit tests Two changes that turned out to be one. MOVED, NOT DELETED. `test/ffsim/` and `test/integration/printer/` are `tools/replica/`. They were never tests: bin/patch.sh calls bin/build-payload.py, which starts a replica and assembles the payload by running the PRINTER'S OWN opkg against / inside it -- so the "test harness" was on the build path, and deleting it as asked would have broken `make build`. qa/lib/replica.py drives the same directory unmodified. No content changed; what changed is qa/lib/replica.py's build directory, three launcher sys.path lines, the Makefile targets and the CI shellcheck glob. tools/replica/README.md says who drives it and why it is not under test/. CUT TO 28. The five surviving modules were 136 tests; they are 28, chosen on one question: would this failure be SILENT? What is kept is the mistakes that run perfectly and are wrong -- test_startup 8 no stamp unless the values are verifiably saved (a stamp written early is a printer that has lost its factory calibration for good), and the handover order test_tool_transform 7 every one is a move to the wrong place: a sign, a frame left applied while probing, a stale gcode_move cache, a config a calibrated printer cannot parse test_ffscreen 5 the four ways it can do harm rather than look wrong test_chamber 4 the chamber mistakes that cost a print before anyone sees them, plus the parse gate they rest on test_gcode 4 a renamed macro, and the safe file being cold What went: the panel narration, the geometry probe and parse_geometry, the z_adjust and per-job-Z bookkeeping, the config layout checks, the G-code bounds checks. Each is either a wrong number shown to a person, or a failure the printer reports loudly the first time -- and qa/replica/test_boot_screen.py already renders the real frames on the real machine. The rewrite is not a delete: assertions were folded so a kept test asks its question in every direction it can be got wrong (both models, both rotations, all four ways the migration can fail), and each file's header now says what it dropped and why, where the next person will open it. Also gone: conftest's `rootfs` fixture, orphaned two commits ago. Nothing under test/ needs the firmware, docker, or a network any more. 28 host-side tests pass in 0.15s. qa/static unchanged at 218. `make rootfs` re-verified end to end from its new path. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UzLebCrvc8ssWR5JuEsha4	2026-08-29 23:27:34 +03:00

Oleksandr ShyshatskyiandClaude Opus 5

56b5b6c334

The printer image is the only replica; make rootfs was a second way nothing took

`make rootfs` unsquashed rootfs.squashfs out of the stock package into
work/rootfs, and a thin container bind-mounted it with PROG_DUMP supplying
/usr/prog from the factory image. Every caller set PRINTER_IMAGE anyway --
both workflows wrote it into test.env BEFORE running `make rootfs`, so CI
unpacked a 93MB package, unsquashed a rootfs and downloaded a 182MB factory
image on every push and read none of it. build-printer-image.sh never used
work/rootfs either: Dockerfile.full does its own extraction from the same
public firmware and needs no stock package at all.

So the fallback went, and PROG_DUMP with it -- it was only ever read when the
replica was built locally, and both implementations already passed it empty
otherwise. Gone: the target, extract-rootfs.py, gates.extract_rootfs and its
two tar helpers, the thin printer/Dockerfile, the `prebuilt` flag threaded
through both Replica implementations, and Replica.start's want_output, whose
only message was that the local build was about to be slow.

PRINTER_IMAGE is pinned to 1.9.7-1.2.9-20260810 rather than :latest. It is
now the entire substrate the brick-safety gates run on and the only input
nothing checksums, so a floating tag would let it change under a green suite
-- the drift the sha256 pins in both workflows exist to prevent.

THREE THINGS THAT COULD NOT HAVE PASSED, found while doing it:

  * Neither workflow built the feed. bin/patch.sh has refused to start
    without one since a1b4ea6, 45 commits after ci.yml was last touched.
    Both ran unpack/patch/pack straight into that guard.

  * `make release` ran bin/build.sh on $(RUN), which has no docker socket,
    while patch.sh assembles the payload inside the replica. `build` has
    used RUNBUILD all along; `release` was left behind. It also built no
    feed. It now builds one, once, outside the per-model loop -- nothing in
    it is model-specific.

  * ci.yml's shellcheck gate named pkgs/*/payload/init.d/S* and
    pkgs/*/prog/*.sh, neither of which exists any more; shellcheck exits 2
    on a path it cannot open. It is a `find` with an asserted count now,
    because the opposite failure is worse: a glob that quietly matches
    nothing checks nothing and still reports green.

Both workflows now go through `make` instead of hand-rolling `docker run`.
Hand-rolling meant CI exercised entry points no human uses, which is exactly
why the `release` runner bug could sit there unseen; it also ran as root and
left a work/ that the later `make release` could not write to.

ci.yml's test job builds the feed before the static lane. A good part of that
lane asks what is inside an .ipk and those questions do not fail without one
-- they return, and the lane reports a pass having never opened a package.
build-packages.sh needs no stock firmware, which is what makes that possible.

Docs, and the packages skill, which still documented pkg_buildopkg and
work/.opkg-host as how the payload is assembled -- the host opkg went in
dcd037c and the printer's own installs the feed now -- and still claimed
qa/static holds an ABI gate over every ELF in every package. It does not:
qa/replica/test_abi.py is the only one, and qa/static asserts a seventh does
not grow back.

Verified: qa/static is 122 passed / 110 errors here, identical to master --
every error is `vendor/opkg-utils is missing` in a checkout that has not run
`make vendor`. mkdocs build --strict passes. The new shellcheck gate was run
as written. The workflows themselves were not executed.

tools/replica/printer/*.sh live inside the published image, so those edits
take effect on the next `make printer-image`; behaviour is unchanged either
way, because nothing sets PROG_DUMP any more.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TrhjKabxDihvVjNQGGT4MK

2026-08-30 14:56:26 +03:00

Oleksandr ShyshatskyiandClaude Opus 5

c185ef3285

The replica is a build tool; test/ is 28 unit tests

Two changes that turned out to be one.

MOVED, NOT DELETED. `test/ffsim/` and `test/integration/printer/` are
`tools/replica/`. They were never tests: bin/patch.sh calls
bin/build-payload.py, which starts a replica and assembles the payload by
running the PRINTER'S OWN opkg against / inside it -- so the "test harness"
was on the build path, and deleting it as asked would have broken `make
build`. qa/lib/replica.py drives the same directory unmodified. No content
changed; what changed is qa/lib/replica.py's build directory, three launcher
sys.path lines, the Makefile targets and the CI shellcheck glob.
tools/replica/README.md says who drives it and why it is not under test/.

CUT TO 28. The five surviving modules were 136 tests; they are 28, chosen on
one question: would this failure be SILENT? What is kept is the mistakes that
run perfectly and are wrong --

  test_startup       8  no stamp unless the values are verifiably saved (a
                        stamp written early is a printer that has lost its
                        factory calibration for good), and the handover order
  test_tool_transform 7 every one is a move to the wrong place: a sign, a
                        frame left applied while probing, a stale gcode_move
                        cache, a config a calibrated printer cannot parse
  test_ffscreen      5  the four ways it can do harm rather than look wrong
  test_chamber       4  the chamber mistakes that cost a print before anyone
                        sees them, plus the parse gate they rest on
  test_gcode         4  a renamed macro, and the safe file being cold

What went: the panel narration, the geometry probe and parse_geometry, the
z_adjust and per-job-Z bookkeeping, the config layout checks, the G-code
bounds checks. Each is either a wrong number shown to a person, or a failure
the printer reports loudly the first time -- and qa/replica/test_boot_screen.py
already renders the real frames on the real machine.

The rewrite is not a delete: assertions were folded so a kept test asks its
question in every direction it can be got wrong (both models, both rotations,
all four ways the migration can fail), and each file's header now says what it
dropped and why, where the next person will open it.

Also gone: conftest's `rootfs` fixture, orphaned two commits ago. Nothing under
test/ needs the firmware, docker, or a network any more.

28 host-side tests pass in 0.15s. qa/static unchanged at 218. `make rootfs`
re-verified end to end from its new path.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UzLebCrvc8ssWR5JuEsha4

2026-08-29 23:27:34 +03:00