Bound X11 lifecycle stress in client CI
Foundation / checks (checks) (push) Successful in 32m0s
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 1m59s
Foundation / checks (postgres) (push) Successful in 44m22s
Foundation / checks (tsan) (push) Successful in 8m3s
Foundation / checks (network) (push) Successful in 5s
Foundation / server-image (push) Successful in 5s
Foundation / image (push) Successful in 10s
Foundation / postgres-tools (push) Successful in 18s

This commit is contained in:
dingo
2026-10-07 15:55:27 -04:00
parent ce1b5b8140
commit 12047503e2
2 changed files with 23 additions and 2 deletions
+14
View File
@@ -5008,3 +5008,17 @@ 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.
## 2026-10-07 — X11 lifecycle check scope
The client CTest lifecycle suite runs 32 full open/event/close cycles with SDL's dummy
video driver. The additional Xvfb invocation runs one full cycle under X11, alongside
the X11 rendering and UI-probe runs. This retains real X11 creation, software rendering,
resize, input/window events, renderer reset/loss and teardown coverage while avoiding a
second 32-cycle stress loop on the Xvfb backend. If `Application::open()` fails in this
test, its output includes the cycle and typed application error before SDL teardown.
Evidence: in the 2026-10-07 Gitea client run, all 13 CTest tests and the X11 probe/UI
smokes passed; only the extra 32-cycle X11 invocation failed at `Application::open()`.
The same 32-cycle lifecycle test passed under SDL's dummy driver. The X11 failure did
not report its typed error, so the failing X11 backend stage was not established.