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
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:
+7
-2
@@ -123,8 +123,13 @@ refusing at 32 (work p95 about 14 ms), with responses about 103 ms and outcomes
|
||||
and its intention admitted (the dev region does not simulate outside drills). M10.9c-2
|
||||
kills and drains a real evo-server under 24 `evo-load` bots. All of them log in to the
|
||||
successor within 5.0 s (SIGKILL, after a 3.5 s lease wait) or 2.4 s (drain), with no failed
|
||||
logins, and responses stay at 106 ms p95. Next: 10.9d, the evolution-dev drill harness and
|
||||
the reference-worker run.
|
||||
logins, and responses stay at 106 ms p95. M10.9d adds the evolution-dev load drill
|
||||
(`tools/ops/load-drill.sh`). It turns synthetic inputs on for the run, drives bundle-mode
|
||||
`evo-load` bots through the public route, and matches each step with the server's 10 s
|
||||
`m10 load-report` log lines. Building it found that Mbed TLS (built without its threading
|
||||
layer) raced when bots verified connections on several threads; one process-wide crypto
|
||||
lock fixed it. Next: the reference run, which needs a promoted image, a load bundle and
|
||||
the maintainer's go-ahead.
|
||||
|
||||
## Previous gate - 2026-10-02
|
||||
|
||||
|
||||
Reference in New Issue
Block a user