Add M10.9d load drill harness and serialize Mbed TLS use
Foundation / checks (deploy) (push) Successful in 3m24s
Foundation / checks (ecs) (push) Successful in 1m56s
Foundation / checks (client) (push) Successful in 12m18s
Foundation / checks (network) (push) Successful in 13m30s
Foundation / checks (tsan) (push) Successful in 8m0s
Foundation / checks (checks) (push) Successful in 32m39s
Foundation / checks (postgres) (push) Successful in 45m47s
Foundation / postgres-tools (push) Successful in 17s
Foundation / image (push) Successful in 2m30s
Foundation / server-image (push) Successful in 4m8s

ADR-0097. tools/ops/load-drill.sh (runbook docs/networking/M10_LOAD_DRILL.md)
runs the evolution-dev reference qualification: synthetic inputs on for
the run (the ADR-0073 drill-time override, restored on exit), bundle-mode
evo-load bots through the public route, and each step's hold matched with
the server's reports. evo-server logs "m10 load-report" every 10 s, since
the agent cannot reach the ops port. evo-load gains --grants FILE
--grants-per-bot C, exhausted=, hold_utc= and close_reasons=;
evo-session-probe grants gains --accounts N.

Finding: Mbed TLS/PSA are built without MBEDTLS_THREADING_C, and bots on
different threads verifying their first connections at once were refused
as untrusted (two per smoke run). One process-wide recursive crypto lock
now guards every network-library entry point that touches them; the
smoke went from 2/2 failing to 3/3 clean. quic-transport adds a
concurrent-connect test. Refreshes the dev session window.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
dingo
2026-10-08 08:38:13 -04:00
co-authored by Claude Opus 5.5
parent 47b84bce74
commit ada77fd761
16 changed files with 609 additions and 70 deletions
+40
View File
@@ -5118,3 +5118,43 @@ Prevention:
- DEPLOYMENT.md documents the Deployment-only sync symptom and the hook re-run.
Executed: deploy policy check (0 failures) and selftest (46 cases, 0 failures).
## 2026-10-08 — M10.9d load drill harness (ADR-0097)
Implemented:
- `tools/ops/load-drill.sh` and its runbook `docs/networking/M10_LOAD_DRILL.md`:
synthetic inputs on for the run (restored on exit), `evo-load` through the public route,
and server reports matched to each hold.
- evo-server `m10 load-report` every 10 s. The agent cannot reach the ops port: no
port-forward, and the API-server proxy is refused.
- `evo-load --grants FILE --grants-per-bot C` with `exhausted=`, `hold_utc=` and
`close_reasons=`; `evo-session-probe grants --accounts N`.
- `include/evo/network/crypto_lock.hpp`: one recursive lock at every Mbed TLS/PSA entry
point of the network library (`MBEDTLS_THREADING_C` is off).
Findings:
- Concurrent first verifications on different threads were refused as `untrusted`, two
per smoke run in bundle mode (2 of 2 runs). With the lock, 3 of 3 runs had no failures.
- The drill summariser, tested on synthetic logs, counted reports from after the hold
(the next step's ramp). Fixed: only reports wholly inside the hold count.
Tests:
- M10 load smoke in bundle mode (8 accounts × 2 grants) with `exhausted=0`.
- The M10 process test checks `m10 load-report`.
- `quic-transport` `concurrent_clients`: 8 threads × 5 rounds all connect. It does not
reliably reproduce the race; the smoke does.
- The lease-loss test's close reasons read 24 × `shutdown` (drain) and 24 × idle
(SIGKILL).
Executed:
- **Linux GCC 14:** presets `quic` and `network` 5/5; `postgres-check.sh` with QUIC, all 18
suites.
- **Linux Clang 19:** clang-tidy 19 on `load.cpp`, the probe, `session_grant.cpp`,
`handoff_ticket.cpp`, `quic_endpoint.cpp`, `quic_transport.cpp`, evo-server `main.cpp`
with the bridge, and the M10 process tests (3 findings fixed); clang-format 19.
- **Windows MSVC 19.44:** presets `quic` 5/5 and `client-network` 15/15.
- **Drill script:** `bash -n`, plus the summariser on synthetic logs; shellcheck is not
installed here.
Not done: the reference run on evolution-dev. It needs this image promoted, a load bundle
and the maintainer's go-ahead.