ui/frontend: cap Playwright at 4 workers, retry 4 times #8

2026-05-15T06:39:42Z

developer commented

2026-05-15 06:39:42 +00:00

Under host-mode runner the default 6 workers / 1 retry lands on ~7 flakies and an occasional hard fail per ui-test run (#59 most recently). Workers share CPU and the host Docker daemon with gitea, the long-lived dev stack, and the host Caddy; the extra wall time from contention pushes individual expectations past their timeouts.

workers: 4 keeps parallelism but gives each worker real CPU headroom.
retries: 4 (was 1) absorbs the rare slow page.

Local pnpm exec playwright test still uses 0 retries (CI-only setting).

Under host-mode runner the default `6 workers / 1 retry` lands on ~7 flakies and an occasional hard fail per ui-test run (#59 most recently). Workers share CPU and the host Docker daemon with gitea, the long-lived dev stack, and the host Caddy; the extra wall time from contention pushes individual expectations past their timeouts. - `workers: 4` keeps parallelism but gives each worker real CPU headroom. - `retries: 4` (was `1`) absorbs the rare slow page. Local `pnpm exec playwright test` still uses 0 retries (CI-only setting).

developer added 1 commit 2026-05-15 06:39:42 +00:00

ui/frontend: cap Playwright at 4 workers, retry 4 times

Tests · UI / test (pull_request) Failing after 26s

Details

Tests · UI / test (push) Successful in 2m21s

Details

7ff81de2b6

Under host-mode runner the default 6 workers + 1 retry consistently
land on ~7 flakies and an occasional hard fail per ui-test run
(ui-test #59 most recently). Workers share CPU and the host Docker
daemon with gitea, the long-lived dev stack, and the user's host
Caddy; the extra wall time from contention pushes individual
expectations past their timeouts.

Lower the worker cap to 4 to keep parallelism but give each worker
real CPU headroom, and raise retries to 4 so the rare slow page is
absorbed without surfacing as failure.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

developer added 1 commit 2026-05-15 06:42:10 +00:00

ci/ui-test: serialise per-ref + clear stale Vite before Playwright

Tests · UI / test (pull_request) Failing after 6s

Details

Tests · UI / test (push) Successful in 2m21s

Details

e3bb30201d

Two ui-test jobs cannot coexist on the same host: Playwright's
`webServer` spec spawns `pnpm dev` on :5173, and on a host-mode
runner the port lives in the host namespace shared by every job.
ui-test #67 hit "Error: http://localhost:5173 is already used"
because a parallel job's Vite still held the port.

Two changes:

1. `concurrency: ui-test-${{ gitea.ref }}` with `cancel-in-progress:
   true`. New push/PR runs against the same ref kill any earlier
   ui-test before starting, so we never have two `pnpm dev`s alive
   at once.
2. `pkill -f 'vite dev' || true` plus `fuser -k 5173/tcp` right
   before Playwright. Defence in depth in case the concurrency
   cancellation does not reap the spawned shell promptly.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

developer added 1 commit 2026-05-15 06:46:01 +00:00

ci/ui-test: key concurrency by head sha, not gitea.ref

Tests · UI / test (push) Has been cancelled

Details

Tests · UI / test (pull_request) Successful in 2m17s

Details

6e6186a571

`gitea.ref` differs between push (`refs/heads/<branch>`) and
pull_request (`refs/pull/N/head`) events even for the same commit,
so the two parallel runs land in different concurrency groups and
the Vite-on-:5173 collision is not suppressed. Switching the key to
the head sha (`gitea.event.pull_request.head.sha || gitea.sha`)
collapses both events into one bucket, leaving exactly one ui-test
alive per commit.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

developer merged commit faf598b2cd into development

2026-05-15 06:49:06 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: developer/galaxy-game#8