2 Commits

Include renames

Author	SHA1	Message	Date
ScottW514	c3da9fa1bd	Catalog: setup.account-login, motion.cancel-abort, forgectrl.settings-bounds and exthost.service leave; the rootfs lint takes image.health's file checks ... The catalog is 43. Each test leaves for a host proof that its component's CI runs at the pins: - setup.account-login: the login rules are host_routes.sh's (forgectrl 6c2bb38); the render is test_image.py's new AccountRenderTests, which runs the layer's forgefirm-users.init with reload in a private mount namespace as root (a fresh /run, the scratch account files over /etc, the scratch data directory, root's, over /data): the data directory found 0700 is 0711 after the render, and as the account's own uid the home is entered and written while listing the data directory and reading the users record are EACCES. A control without the script's chmod go+x fails it (700 != 711). forgectrl.auth's cover widens to src/ui/login.*, since login.html had no other cover. - motion.cancel-abort: laser_lifecycle_test.py's new rule 17 on the null-sink controller: 0x85 stops a jog short of its target, Idle; ^X mid-move lands in Alarm with the position kept and no return to the job start; $X recovers to Idle and the next jog ships steps (counted in GFSINK_DUMP). It passes on the driver at its pin, badc832. motion.deadman requires motion.pacing in its place. - forgectrl.settings-bounds: host_routes.sh refuses the out-of-range and over-length values with the settings file byte for byte the same, and the lid lamp under GF_SYSFS_ROOT follows lid_lamp_idle (forgectrl 6c2bb38). - exthost.service: forgeext's host tests at the pinned bb75b23 - sandbox_test (the confinement from inside, the pulse device, the settings file and the setup record refused), run_test.py (the API, safe mode, the master switch, and the killed host under the init script's own wrapper), install_test.py and sdk_test.py. exthost.armed-freeze requires exthost.platform in its place. HOST_TESTED rows for each path the lint named once exthost.service left: forgectrl src/logs.* to logs_test.c and docs/advisories/extensions.md to host_setup.sh; forgeext src/api.*, caps.*, evfeed.*, holdkeep.*, httpreq.*, manifest.*, quota.*, sandbox.*, settings.*, state.* to their unit tests, netrules.* to netrules_test.py, call.* to sdk_test.py, install.*, pkg.* and index.* to install_test.py, and main.c, fflog.* and CMakeLists.txt to run_test.py. test_manifest's behavioral-path case is unaffected. The rootfs lint takes image.health's file checks (rules init-order, logging, watchdog, read-only, dhcpv6, and on a release image factory), each proved in RootfsLintTests by a drift that fails it. image.health keeps the live half: the rendered issue and motd against the running manifest, one host and no pool process, watchdog0, no userspace watchdog running, the mounts, the dev image's factory slots read-only, no DHCPv6 client running, the DHCP client's -b and parent, ifup, the getty, and IPv6. release.sh drops its PermitRootLogin and PermitEmptyPasswords greps, its ROOTFS_READ_ONLY check and its /factory fstab check, which the lint holds; it keeps the empty root shadow field, / mounted ro, and the three HostKey lines under /data. setup.py registers no test now: its helpers the deleted tests alone called go (tls_base, tcp_open, mode, press_status, wiz_summary, wait_settled, the login constants), and test_setup_suite.py keeps the cases of what remains. Fingerprints: image.health's moves (its text), every test in exthost.py, forgectrl.py and motion.py moves with its module text, and the layer content hash moves with rootfs-lint.sh: the next image inherits no campaign. Proof: the coverage lint over the tree manifest from the pins finds 0 uncovered paths and 0 host-tested row problems (43 tests); pyflakes on the touched files is clean; forgetest's unit suite under Linux passes (334), test_image.py's 28 among them. The lint passes image 20261015142442's release tree as release and its dev tree as dev, and refuses the dev tree as release (sshd, factory). laser_lifecycle_test.py passes whole on the null-sink build of badc832.	2026-10-15 14:02:20 -04:00
ScottW514	08c7df9cbb	rootfs-lint.sh: the image content fixed at build time, checked as the last rootfs step ... A new script beside the image recipe, run by both images as the last rootfs step (ROOTFS_POSTPROCESS_COMMAND:append, after every +=, the dev recipe's and debug-tweaks' included); a refusal is bbfatal. It checks every rule and prints every failure before it exits. FORGEFIRM_IMAGE_KIND (release by default, dev in forgefirm-image-dev.bb) picks the sshd policy. The rules: - syslog: /usr/sbin/rsyslogd is on the image, /etc/init.d/syslog starts it and runlevel 5 starts that script; no syslogd or klogd is linked in a bin directory and no init script runs one. This is the image half of what logs.routing checked on the board; that test left in 01f5991 with nothing else holding it. - sshd: sshd_config and sshd_config_readonly take passwords (PasswordAuthentication yes) and send no banner; on a release image PermitRootLogin no and PermitEmptyPasswords no; sshd_config.d sets none of the four, since an included value comes first. setup.ssh-until- reboot checked the first two on the board and left in 01f5991; release.sh gates the release pair at release time only. - dhcp-name: the wlan0 dhcp stanza's udhcpc_opts carries -x hostname:$(hostname). - mdns: no /etc/avahi, avahi-daemon or libnss_mdns, and no mdns source on nsswitch.conf's hosts line. dhcp-name and mdns are the image half of setup.machine-name, whose scripts test_image.py's MachineNameTests already run. test_image.py's RootfsLintTests run it on a fixture tree: the tree that holds every rule passes as either image, the BSP layer's own interfaces file passes, and one drift per rule fails naming the rule (a busybox syslogd link; a Banner, on either image; root and an empty password, refused on a release image and passed on a dev one; a dhcp stanza with no name; /etc/avahi). Proof: test_image.py under Linux, 21 OK; pyflakes clean. On image 20261015134521's two rootfs trees from the build, the release tree passes as release, the dev tree passes as dev, and the dev tree linted as release is refused on PermitRootLogin and PermitEmptyPasswords in both sshd files. bitbake -e places rootfs_lint last in both images' ROOTFS_POSTPROCESS_COMMAND, with FORGEFIRM_IMAGE_KIND release and dev. The layer content hash moves: the next image cannot inherit a campaign.	2026-10-15 10:19:54 -04:00