From ef7cbdffd461ede1601f16b4615a08f2de55c2b1 Mon Sep 17 00:00:00 2001 From: ETWen Date: Tue, 25 Aug 2026 14:22:22 +0800 Subject: [PATCH] docs(release): Add v1.0.7 notes; bump Script A header to V1.0.7 Script A carried a V1.0.7 history block while its "; Version :" header still read V1.0.6, so publish.sh built Script_ABC_Blanton_V1.0.6 and the folder would have disagreed with the tag. Header and date corrected -- reading the version from the header rather than a flag is what surfaced this. utils/wait_init.ttl V3.1.1: poll interval 10 s -> 60 s, and the WT_MIN comments now say "at least" to match the test, which has been `< WT_MIN` since the threshold was fixed. The stale "more than" wording described exactly the off-by-one that once hung Script A. Script C: the BMC USB journalctl dump is commented out. docs/release-notes/v1.0.7.md written in the house format. Co-Authored-By: Claude Opus 5 (1M context) Claude-Session: https://claude.ai/code/session_014RetWKFZFG1ZHcitQAyhwM --- docs/release-notes/v1.0.7.md | 65 +++++++++++++++++++ src/Script_ABC_Blanton/1_Blanton_Script_A.ttl | 6 +- src/Script_ABC_Blanton/3_Blanton_Script_C.ttl | 4 +- src/Script_ABC_Blanton/utils/wait_init.ttl | 11 +++- 4 files changed, 79 insertions(+), 7 deletions(-) create mode 100644 docs/release-notes/v1.0.7.md diff --git a/docs/release-notes/v1.0.7.md b/docs/release-notes/v1.0.7.md new file mode 100644 index 0000000..fa8e596 --- /dev/null +++ b/docs/release-notes/v1.0.7.md @@ -0,0 +1,65 @@ +# v1.0.7 — Management-link ping test, and the fans start where you set them + +## ✨ New features + +**10G / 1G management port ping test** +* New `mgmt_ping_monitor.sh` exercises both management NICs in one loop: it brings each up with iproute2, waits for the link to settle, then pings that NIC's own target — `eth0` → `192.168.1.30`, `eth1` → `192.168.1.31`. +* Runs detached like the other monitors: `start` / `stop` / `status` / `fg` / `summary`. `start` clears the previous log, so one run means one log. +* Every leg writes a single greppable line — `RESULT 10G eth0 -> 192.168.1.30 tx=10 rx=10 loss=0% rtt_avg=1.743ms nic_tx=10 nic_rx=10 PASS` — so a whole soak can be read with `summary` instead of scrolling. +* `nic_tx` / `nic_rx` are that interface's own counter delta across the burst. If a ping passes but they stay near zero, the traffic left on the *other* NIC and the number does not belong to this one. +* Script A runs one round as a baseline; Script B leaves it running through the soak. + +**Fan speed is set at the start of every run** +* `FAN_SPEED` in `config.ttl` (default 30) is applied by Script A, so a run no longer inherits whatever the previous test left the fans doing. +* Both MAX31790 controllers are rebound first, which clears a controller left in an odd state. + +**Stress load moved onto the platform's own job runner** +* CPU, DDR, SSD and USB stress now go through `bgctl`, replacing the `~/hammer/tools/stress_*.py` scripts. `bgctl list` shows what is running; Script C stops everything with `bgctl stop --all`. +* BMC DDR stress runs through `bmc-manager`, and a new BMC USB test discovers the `cdc_ncm` interface and pings across it for four hours under `systemd-run`. + +**More of the DUT on record** +* Script A now captures the boot image, `show version`, firmware status, system EEPROM, SSD health, TPM version and NVMe SMART data before the test starts. +* PCIe AER now sits next to `ras-mc-ctl --summary`, and Script C closes with NVMe health so a disk that degraded during the soak is visible. +* `dmesg` capture uses human-readable timestamps and one combined error pattern, then clears the ring buffer — so Script C's dmesg shows only what the soak produced, not everything since boot. +* Each run opens with `hw-test-session start` and closes with `finish`; Script C copies the job logs to `/mnt/usb/jobs-_