Fix CI test-runners health check for DinD networking
Some checks failed
CI/CD / detect-changes (pull_request) Successful in 21s
CI/CD / test-frontend (pull_request) Successful in 5s
CI/CD / test-go-pg (pull_request) Successful in 2m35s
CI/CD / test-sqlite (pull_request) Successful in 3m20s
CI/CD / build-and-deploy (pull_request) Has been cancelled
CI/CD / test-runners (pull_request) Has been cancelled

In Gitea runner pods, docker compose port mapping (3000:80) doesn't
expose to the runner container's localhost. Resolve the armature
container IP via `docker inspect` and pass it directly to the health
check and Playwright test runner.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
2026-04-02 08:58:29 +00:00
parent 698ea091ed
commit 4a4160300b
2 changed files with 13 additions and 2 deletions

View File

@@ -150,6 +150,7 @@ Design doc: `docs/DESIGN-surface-runners.md`
| Renderer runner | done | `requires: ["mermaid-renderer"]`. 1 suite (contract), 4 tests. |
| Runner result API | done | `POST/GET /api/v1/admin/test-runners/results`. In-memory store, 4 Go tests. |
| CI integration | done | `test-runners` stage in Gitea CI. Playwright driver, `wait-for-healthy.sh`. |
| CI DinD networking fix | done | Resolve container IP via `docker inspect` — DinD port mapping doesn't expose to runner localhost. |
### v0.7.3 — Extension Shell Migration + Headless E2E