Fix CI: run M10 process tests with the load governor off
Foundation / checks (deploy) (push) Successful in 3m15s
Foundation / checks (ecs) (push) Successful in 1m57s
Foundation / checks (client) (push) Successful in 12m33s
Foundation / checks (network) (push) Successful in 13m19s
Foundation / checks (tsan) (push) Successful in 8m5s
Foundation / checks (checks) (push) Successful in 32m42s
Foundation / checks (postgres) (push) Successful in 43m45s
Foundation / postgres-tools (push) Successful in 20s
Foundation / server-image (push) Successful in 24s
Foundation / image (push) Successful in 2m31s

checks (postgres) failed on both M10.9 pushes: on the shared CI runner one
session measured 22 ms p95 per tick, so the governor correctly refused
and the test's assumption about host speed failed (server-image was
skipped as a result). evo-server gains --m10-load-governor on|off (dev
only): off keeps measuring and exposing the work but never refuses or
sheds. The M10 session, load-smoke and two-process handoff tests use it;
the governor stays covered by its unit tests. Refreshes the dev session
window.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
dingo
2026-10-07 11:58:37 -04:00
co-authored by Claude Opus 5.5
parent 1ba6748288
commit 66efe87c90
6 changed files with 77 additions and 26 deletions
+20
View File
@@ -4988,3 +4988,23 @@ Executed:
Not done:
- the reference-worker run (10.9d);
- the abuse suite (10.9c).
## 2026-10-07 — CI correction for M10.9a/b (ADR-0097)
With agent access to Gitea Actions it became visible that `checks (postgres)` had failed
on both M10.9 pushes (`b8cb9db`, `1ba6748`). The `server-image` and `image` jobs were
therefore skipped, and the last published server image is still from `97a3756`. The local
runs recorded above passed, but CI is the authority and was red.
Cause: `region_m10_session_tests` asserted that a lightly loaded region is not refusing.
On the shared CI runner (Release build) one session measured work p95 22 ms and p99 37 ms
(session layer p99 22 ms), so the load governor correctly refused, and the test's
assumption about host speed failed.
Fix: evo-server gains `--m10-load-governor on|off` (dev only; default on). With `off`,
work is still measured and exposed, but nothing is refused or shed, and the gauges report
refusing 0 and shed 0. The M10 session, load-smoke and two-process handoff tests use it;
the governor itself remains covered by its unit tests.
Executed: local `postgres-check.sh` with QUIC, all suites. The CI result for this commit
is checked via the Gitea API after the push.