Run client lifecycle tests from path selector
Foundation / checks (deploy) (push) Successful in 18s
Foundation / checks (ecs) (push) Successful in 1m57s
Foundation / checks (tsan) (push) Successful in 8m41s
Foundation / checks (client) (push) Successful in 13m15s
Foundation / checks (network) (push) Successful in 15m42s
Foundation / checks (postgres) (push) Failing after 23m53s
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 25m33s

This commit is contained in:
dingo
2026-10-11 16:42:21 -04:00
parent b99bb1b403
commit 8492ded303
3 changed files with 10 additions and 1 deletions
+6
View File
@@ -6988,3 +6988,9 @@ That failure gates `server-image`; the test now reports its typed open error and
checks SDL teardown after each test section so the next CI run can identify the
failing lifecycle boundary. The PostgreSQL integration and static-analysis job
is still running; no Harbor publish has started.
CI run #300 did not rerun the client suite: the path selector omitted
`tests/client_lifecycle.cpp`, so it treated the diagnostic-only commit as
irrelevant. The client selector and its offline regression fixture now include
that test source. The next CI run must execute the diagnostics before its client
result can be used to unblock the server image.