feat(tools): soak-check.sh + HARDWARE.md soak runbook — the identical stress test for any box - #442
Merged
Merged
Conversation
… stress test for any box One read-only script per checkpoint: firmware/throttle (incl. the config.txt overclock trap), restarts/OOM, memory snapshot, disk/NFS, /health, stream truth (icecast log + /proc/net/tcp — status-json hides mounts by design), safe-branch engagements from docker-side UTC timestamps, render pressure, error counts. Validated live against the Pi 5 at day 7 — where it caught three ~2s safe-branch blips the manual checkpoint missed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Dean's ask before Pi 4 testing: the soak procedure as a runnable, documented artifact. 🧪
What ships
tools/soak-check.sh— one read-only command = one checkpoint: every step-8 criterion as a ✅/❌ line plus the memory snapshot to record. Runs on the box or viassh <box> 'bash -s' < tools/soak-check.sh.docker logs -tonly; docker-exec-inside-cgroup measurement hazard; known-benign error lines).Validation
Run live against the Pi 5 at day 7 of its soak. It works — and it immediately caught what my manual checkpoint had missed: three ~2s safe-branch engagements (Aug 7 19:58 / 22:04, Aug 8 04:44 UTC, all in one overnight band, none in the 36h since, no correlated api warnings). Strict criterion says those are reds; whether ~6 seconds of safe-branch across 168 hours passes the 7-day bar is Dean's call — the tool's job is that nobody has to notice by ear.
Second run after the engagement-counting refinement confirms: only switches AWAY from the main queue count; paired recovery switches are informational.