Add M10.6c probe-marker prediction traces and close M10.6
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 1m54s
Foundation / checks (postgres) (push) Canceled after 0s
Foundation / checks (tsan) (push) Canceled after 0s
Foundation / postgres-tools (push) Canceled after 0s
Foundation / server-image (push) Canceled after 0s
Foundation / image (push) Canceled after 0s
Foundation / checks (checks) (push) Canceled after 12m33s
Foundation / checks (network) (push) Canceled after 10m23s
Foundation / checks (client) (push) Canceled after 12m33s

evo-motion-trace drives the engineering client's own session code through
the owned impairment relay against a real-time 50 ms loopback region:
exact without loss, 94-99 % exact at 60-200 ms RTT with 2-5 % loss, every
profile converging after stopping, restart resync about 2-3 s
(docs/networking/M10_PREDICTION_TRACES.md). The CTest motion-trace-smoke
checks convergence, bounds and a majority of exact predictions.

The relay lets a new sender take over after the current client has been
silent for 1 s (reconnects); the client counts refusal receipts.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
dingo
2026-10-06 17:03:45 -04:00
co-authored by Claude Opus 5.5
parent 96237ca10a
commit 61d899de3c
12 changed files with 518 additions and 12 deletions
+41
View File
@@ -4562,3 +4562,44 @@ clang-format 19 was applied to the changed files.
Not done:
- impaired traces (10.6c);
- a GUI run against evolution-dev, which needs a v3 server.
## 2026-10-06 — M10.6c prediction traces (ADR-0094)
Implemented:
- `evo-motion-trace` (the client's own session code through the impairment relay against
a real-time 50 ms loopback region);
- the CTest `motion-trace-smoke`;
- the relay takeover by a new sender after the current client has been silent for 1 s;
- a refusal count in the client status, replacing the unused predictor field.
Figures are in docs/networking/M10_PREDICTION_TRACES.md. Linux, one run of each profile:
- clean and lan: 100 % exact;
- rtt60-loss2: 97.9 %;
- rtt120-loss2: 99.3 %; restart resync 2,946 ms;
- rtt200-loss5: 94.1 %; p99 500 mm, max 989.9 mm.
Every profile converged after stopping. Windows was similar, with a maximum of 1,399.8 mm
at rtt200-loss5. The smoke profile passed 3 times in a row on Linux.
Found and fixed during development:
- the relay ignored a reconnecting client (new source port), so restart resync timed out;
- refusals were undercounted when an input had already been dropped;
- a clang-tidy widening-cast finding.
Executed:
- **Linux GCC 14**
- preset `client-network`: CTest 15/15, including motion-trace-smoke and
client-remote-session;
- preset `quic`: 4/4, including quic-transport with the changed relay.
- **Linux Clang 19:** clang-tidy 19 on the trace tool, client app, remote test, predictor
and relay.
- **Windows MSVC 19.44** (fresh binaries):
- preset `quic`: 4/4;
- preset `client-network`: 13/13, including motion-trace-smoke;
- a full trace run.
The Postgres suite was not rerun: no server code changed since 10.6b.
Not done:
- traces over the dev route (a v3 server must be deployed first);
- many-client load (10.8).