c3b0d491457fd2898afd9dd9c2d865b8287851f4
After a run that ended badly - Tera Term closed, DUT rebooted mid-soak, macro stopped by hand - the stress jobs kept running and the test session stayed open. The next run then started on a box that was already loaded. Nothing errored; the numbers were just quietly wrong. Script A now opens with hw-test-session finish, bgctl reset --yes, bgctl stop --all, then bgctl list. The list is the point of the sequence: it is the one line in the log that proves the DUT was idle at the start. Script A -> V1.1.1. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014RetWKFZFG1ZHcitQAyhwM
Description
Blanton Tera Term TTL reliability test
4.2 MiB