Skip to content

ci: supervise Laravel server during Windows browser certification - #145

Merged
wpessential merged 3 commits into
mainfrom
ci/windows-e2e-server-supervisor-2026-10-08
Oct 8, 2026
Merged

wpessential merged 3 commits into
mainfrom
ci/windows-e2e-server-supervisor-2026-10-08

Conversation

@wpessential

Copy link
Copy Markdown
Contributor

Scope

Keep the local Laravel app server available throughout Playwright certification, with bounded recovery when health checks fail or the child exits.

Evidence

Windows Certification on PR #144 (2decd8eaf12dd1dc2506e2852c26df4acc920c10) passed the application/runtime checks and standard responsive E2E, then failed during actual Chrome/Edge/Firefox accessibility coverage because 127.0.0.1:8777 began refusing connections. The captured logs contained no PHP fatal or restart explanation. This PR addresses only the test harness server lifecycle.

Changes

  • launch Laravel through a small Node supervisor from Playwright webServer
  • probe /health/live with bounded timeouts and startup grace
  • restart at most twice on process exit or repeated unhealthy probes, then fail with a circuit breaker
  • terminate the Windows process tree on shutdown

Verification

Fresh exact-head CI, including Windows Certification, is required. No product code, production environment, provider credentials, migrations, release or Runner authorization are changed.

@wpessential
wpessential merged commit dfb4fc7 into main Oct 8, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant