Files
forgefirm/kas/forgefirm-glowforge-debug.yml
ScottW514 88ec984e28 Audit follow-through: runbook, bench tools, recipes, release tooling
BRINGUP describes the present: the 54-test catalog and its seven-test
always core, the tier counts, the shipped low-temperature gates, the
density floor ($35 = 10), the two local core commits, the ffboot env
write, the aa-offset route, the current bench image, and the bench
measurements the audit asks for (pooled into the next session). The
workstation shell notes and every em dash are gone.

forgetest: the takeover waits for the cloud client too (found by its
command line); the unauthenticated /boot probe names the endpoint's
parameter; the UI prose is American English. Recipes: forgetest
fetches its package directory and init script only and drops
__pycache__ at unpack; the dev image no longer re-adds forgectrl; the
release image's remove list drops the gfui-client the BSP no longer
has; the platform identity strips the kernel's local-version hash
from the modules directory name, so a re-patched kernel keeps its
fingerprints. grblhal restart is stop then start. release.sh --dev
packs the dev image. fixture.sh refuses a readable env file.

Bench tools: the live-fire drills measure the lid-IR baseline before
every run and point at the fire-watch thresholds the engine reads;
one thermistor conversion (gfbench.degc) serves every drill; the six
dated measurement records leave the tool directory; feeder.c names the
two sysfs writes its caller makes.

Host tests: forgetest 258 pass; the coverage lint reports no uncovered
path across 54 tests. Acceptance: forgectrl.auth covers the /boot
probe; update.* cover ffboot and the manifest identity; the runbook
and bench-tool changes have no catalog consequence.
2026-09-02 09:51:23 -04:00

37 lines
1.7 KiB
YAML

# ============================================================================
# ForgeFIRM - debug-kernel build variant
# ============================================================================
# One target: a dev image whose kernel carries the lock-correctness options
# (DEBUG_MUTEXES, PROVE_LOCKING, DEBUG_ATOMIC_SLEEP, DEBUG_SPINLOCK). It rides
# the closing build: after the normal release + dev images build, one pass of
# this config produces a dev image tagged "(dev-debug)". The bench boots it
# once to run the module load/unload and forced -EPROBE_DEFER drills
# (forgefirm/scripts/bench/debug_kernel_drills.py), then the real image is
# flashed. The options never touch a release or a normal dev build.
#
# cd forgefirm
# kas build kas/forgefirm-glowforge-debug.yml
#
# The debug kernel has a different config signature, so bitbake rebuilds the
# kernel and the dev image under it without disturbing the images already in
# build/tmp/deploy/images/glowforge/; the debug dev image lands beside them
# with its own DATETIME stamp and the "(dev-debug)" version string.
# ============================================================================
header:
version: 14
includes:
- forgefirm-glowforge.yml
target: forgefirm-image-dev
local_conf_header:
debug-kernel: |
FORGEFIRM_KERNEL_DEBUG = "1"
FORGEFIRM_VERSION_STRING:pn-forgefirm-image-dev = "${DATETIME} (dev-debug)"
FORGEFIRM_VERSION_STRING[vardepsexclude] += "DATETIME"
# A distinct deploy basename so the debug image does not share the dev
# image's single deploy slot and clobber it. It lands as
# forgefirm-image-dev-debug-glowforge.rootfs-*.wic.gz beside the others.
IMAGE_BASENAME:pn-forgefirm-image-dev = "forgefirm-image-dev-debug"