Kaj SchittecatandClaude Opus 5
66e1f37d2c
Two things made a full harness run untrustworthy, and together they produced a false accusation against a community app. wada.fs was stubs. append threw the data away, remove always said true, and read, write and list were not there at all — although the firmware registers all five (LuaAppHost.cpp). Any app that writes a file and reads it back therefore failed here while working perfectly on device. wardrive 1.2 is exactly that app: it errors on a nil fs.read at its first log flush, long before it renders anything, and the emoji scenario then reported the repeater name as unrendered. Read as "1.2 regressed the beta_70 emoji fix", which it did not. It passes untouched once fs is real. wada.fs is now an in-memory filesystem following LuaAppHost's semantics: read returns the data plus the file's TOTAL size so a caller can window a growing log, an offset at or past the end gives an empty string rather than nil, a missing file gives nil, and list is sorted so a hash order cannot make a test flaky. The second: the gpscompass scenario list was acting as the dispatch default, so an app with no branch of its own was run against tests written for a different app. Six store apps have no branch (2048, airtime, monitor, nearby, sdktest, snake), so a full sweep came back with six red apps as its normal state — and a real regression would not have stood out against that. Those apps now say they have no scenarios and run none. They are untested, which is worth saying out loud, but that is not the same as broken. A sweep of every store app is now 8 apps passing their own scenarios, 6 reported untested, 0 failures. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Host harness for Wadamesh Lua apps
Runs a Store app on your desktop, against a mock of the wada.* host, before
it ever touches a device. Not part of the firmware build.
scripts/lua-harness/run.sh # gpscompass, all scenarios
scripts/lua-harness/run.sh deploy/apps/wardrive/1.1/wardrive.lua
SCENARIO=declination scripts/lua-harness/run.sh # one scenario
run.sh compiles luah on first use (and whenever main.c changes) from the
Lua sources already vendored in lib/lua/src — no dependency beyond a C
compiler.
What makes it worth running
It is built from the same vendored Lua 5.4.7 as the firmware, with the same
LUA_32BITS numeric model — 32-bit integers, single-precision floats. That
is the point. Maths that behaves in a desktop float64 interpreter can lose
catastrophic precision on the device, and this is where that shows up.
The mock mirrors LuaAppHost.cpp rather than being convenient: the same
argument type-checks, the same 100k-instruction budget per callback, the same
event shapes, and the same store restrictions. That has caught real defects —
the device store accepts strings and numbers only, and a boolean flag thrown
inside a guarded callback looks exactly like a keypress doing nothing at all.
Device attitude is simulated physically, not faked: a magnetic field of the right magnitude and dip, rotated into the body frame by heading/roll/pitch, plus the hard-iron and zero-g biases measured on a real M9. So calibration, tilt compensation and heading all get exercised for real.
Scenarios
harness.lua holds them all. Board shapes — M9 320x196 landscape, V4/R8
portrait, base-SDK V4 (no extended SDK), Pager, Pager portrait at Jumbo font
sizes, Tanmatsu — plus an instruction-cost probe that fails the run if any tick
exceeds a quarter of the budget.
Three are about the compass being correct rather than merely working:
declination— pulls the generated WMM block straight out of the app file and checks it against NOAA reference values at six sites, including a weak-field one near the pole. Testing the shipped bytes, not a copy, so a bad regeneration fails here rather than on hardware. Seescripts/wmm/.bearings_absolute— contacts placed due N/E/S/W and NE of the fix, to check bearings against absolute compass directions. The older marker test compares each drawn dot against the app's own bearing, which stays self-consistent even if east and west are swapped; this one would not. The north-east case is what separates a mirror from a lat/lon transpose (38.3° vs 51.7°).align_nofix— "set north" pressed with no position at all. The offset it stores silently swallows the whole declination, so the app has to give it back when the first fix lands, or the heading is wrong by twice it.
Reading a failure
Scenarios print what they saw before asserting, so a failure usually names the cause. Two conventions worth knowing:
- The dial centre is read out of the canvas draw order: digits, degree sign, T/M reference, cardinal. Add anything to that sequence and the index offsets in the assertions move with it.
APP ERROR:means the app raised inside a guarded callback — the harness keeps going, and the scenario fails later on a symptom. The firstAPP ERRORline is the real one.